org.texi (Pushing to MobileOrg): Mention that `org-directory' should not contain symbolic links
* org.texi (Pushing to MobileOrg): Mention that `org-directory' should not contain symbolic links. Thanks to James Harkins for reporting this problem.
This commit is contained in:
parent
7b26ec60a9
commit
76684b5606
20
doc/org.texi
20
doc/org.texi
|
@ -16555,14 +16555,18 @@ to the directory @code{org-mobile-directory}. By default this list contains
|
||||||
all agenda files (as listed in @code{org-agenda-files}), but additional files
|
all agenda files (as listed in @code{org-agenda-files}), but additional files
|
||||||
can be included by customizing @code{org-mobile-files}. File names will be
|
can be included by customizing @code{org-mobile-files}. File names will be
|
||||||
staged with paths relative to @code{org-directory}, so all files should be
|
staged with paths relative to @code{org-directory}, so all files should be
|
||||||
inside this directory. The push operation also creates a special Org file
|
inside this directory@footnote{Note that symbolic links are not supported,
|
||||||
@file{agendas.org} with all custom agenda view defined by the
|
you need to store files @emph{physically} in @code{org-directory}.}.
|
||||||
user@footnote{While creating the agendas, Org mode will force ID properties
|
|
||||||
on all referenced entries, so that these entries can be uniquely identified
|
The push operation also creates a special Org file @file{agendas.org} with
|
||||||
if @i{MobileOrg} flags them for further action. If you do not want to get
|
all custom agenda view defined by the user@footnote{While creating the
|
||||||
these properties in so many entries, you can set the variable
|
agendas, Org mode will force ID properties on all referenced entries, so that
|
||||||
@code{org-mobile-force-id-on-agenda-items} to @code{nil}. Org mode will then
|
these entries can be uniquely identified if @i{MobileOrg} flags them for
|
||||||
rely on outline paths, in the hope that these will be unique enough.}.
|
further action. If you do not want to get these properties in so many
|
||||||
|
entries, you can set the variable @code{org-mobile-force-id-on-agenda-items}
|
||||||
|
to @code{nil}. Org mode will then rely on outline paths, in the hope that
|
||||||
|
these will be unique enough.}.
|
||||||
|
|
||||||
Finally, Org writes the file @file{index.org}, containing links to all other
|
Finally, Org writes the file @file{index.org}, containing links to all other
|
||||||
files. @i{MobileOrg} first reads this file from the server, and then
|
files. @i{MobileOrg} first reads this file from the server, and then
|
||||||
downloads all agendas and Org files listed in it. To speed up the download,
|
downloads all agendas and Org files listed in it. To speed up the download,
|
||||||
|
|
Loading…
Reference in New Issue