From: James Harkins <jamshark70@gmail.com>
To: "Emacs-orgmode@gnu.org" <Emacs-orgmode@gnu.org>
Subject: org-mobile-push vs. symlinks
Date: Sat, 8 Dec 2012 11:42:52 +0800 [thread overview]
Message-ID: <CAFniQ7WEumCcPmpGAY+4EWGg0kGU8ZRL6vpmstnw_DYDAmQkHQ@mail.gmail.com> (raw)
In-Reply-To: <CAFniQ7WZdy3v3cCNN8PPJg796Qq-+VS-jfiAimr8qvxnH2gJcg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
I had a problem with mobile org sync, which I finally tracked down to the
handling of symlinks in org-mobile-push.
Setup: I want to have a different file name for my school org file
depending on fall or spring semester, but I hoped to avoid changing
org-agenda-files once a semester. So I symlinked semester-fall.org to
~/Documents/mobileorg/semester.org.
It seems that org-mobile-push resolves the symlink to determine the
filename to drop into the online share. So MobileOrg knows about
semester-fall.org, but there is no file by that name in org-directory. So,
org-mobile-pull opens an empty buffer for semester-fall.org and, as it's
empty, of course the parent node can't be found.
My question: Is there a technical reason why org-mobile-push must use the
symlink target's filename, instead of the filename that actually lives
under org-directory? Other parts of the code assume the filename under
org-directory. I can think of two possibilities:
- One should not put symlinks into org-directory, or at least make sure the
symlink's name is the same as the target. If this is an intentional
limitation, it should be documented.
- Or, the symlink resolution is not actually necessary and it causes
problems. In that case, it's a bug that should be fixed.
Which is it? :-)
hjh
[-- Attachment #2: Type: text/html, Size: 1520 bytes --]
next parent reply other threads:[~2012-12-08 3:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFniQ7U88AmmeQj8rXW87YKRTjXyx=GqTYfJUrbtEyGWeQnrwA@mail.gmail.com>
[not found] ` <CAFniQ7WGYWEnd8BxoVVOegLfsb+uCYzeVxx0emgywnutqP+46g@mail.gmail.com>
[not found] ` <CAFniQ7WfWKpUyzMZVhiChjQekOP_ZZSUV17=iR4ZiVLtPCOpow@mail.gmail.com>
[not found] ` <CAFniQ7WZdy3v3cCNN8PPJg796Qq-+VS-jfiAimr8qvxnH2gJcg@mail.gmail.com>
2012-12-08 3:42 ` James Harkins [this message]
2012-12-15 8:49 ` org-mobile-push vs. symlinks James Harkins
2012-12-15 8:57 ` Bastien
2012-12-19 17:57 ` J. David Boyd
2012-12-19 18:09 ` Bastien
2013-01-03 12:10 ` Bastien
2013-01-04 9:50 ` James Harkins
2013-01-04 15:34 ` Bastien
2013-01-06 9:59 ` James Harkins
2013-01-06 13:57 ` Bastien
2013-01-07 2:34 ` James Harkins
2013-01-07 2:42 ` Bastien
2013-01-07 17:21 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFniQ7WEumCcPmpGAY+4EWGg0kGU8ZRL6vpmstnw_DYDAmQkHQ@mail.gmail.com \
--to=jamshark70@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).