Next: , Previous: Setting up the staging area, Up: MobileOrg

B.2 Pushing to MobileOrg

This operation copies all files currently listed in org-mobile-files to the directory org-mobile-directory. By default this list contains all agenda files (as listed in org-agenda-files), but additional files can be included by customizing org-mobile-files. File names will be staged with paths relative to org-directory, so all files should be inside this directory1.

The push operation also creates a special Org file with all custom agenda view defined by the user2.

Finally, Org writes the file, containing links to all other files. MobileOrg first reads this file from the server, and then downloads all agendas and Org files listed in it. To speed up the download, MobileOrg will only read files whose checksums3 have changed.


[1] Symbolic links in org-directory need to have the same name than their targets.

[2] While creating the agendas, Org mode will force ID properties on all referenced entries, so that these entries can be uniquely identified if MobileOrg flags them for further action. If you do not want to get these properties in so many entries, you can set the variable org-mobile-force-id-on-agenda-items to nil. Org mode will then rely on outline paths, in the hope that these will be unique enough.

[3] Checksums are stored automatically in the file checksums.dat