org-mobile-pull synchronizes changes with the server. More specifically, it first pulls the Org files for viewing. It then appends captured entries and pointers to flagged or changed entries to the file ‘
mobileorg.org’ on the server. Org ultimately integrates its data in an inbox file format, through the following steps:
Org moves all entries found in ‘
mobileorg.org’1 and appends them to the file pointed to by the variable
org-mobile-inbox-for-pull. It should reside neither in the staging area nor on the server. Each captured entry and each editing event is a top-level entry in the inbox file.
After moving the entries, Org processes changes to the shared files. Some of them are applied directly and without user interaction. Examples include changes to tags, TODO state, headline and body text. Entries requiring further action are tagged as ‘
FLAGGED’. Org marks entries with problems with an error message in the inbox. They have to be resolved manually.
Org generates an agenda view for flagged entries for user intervention to clean up. For notes stored in flagged entries, Org displays them in the echo area when point is on the corresponding agenda item.
?displays the entire flagged note in another window. Org also pushes it to the kill ring. To store flagged note as a normal note, use
? z C-y C-c C-c. Pressing
?twice does these things: first it removes the ‘
FLAGGED’ tag; second, it removes the flagged note from the property drawer; third, it signals that manual editing of the flagged entry is now finished.
From the agenda dispatcher,
? returns to the view to finish processing flagged entries. Note that these entries may not be the most recent since the mobile application searches files that were last pulled. To get an updated agenda view with changes since the last pull, pull again.
- The file will be empty after this operation.↩