From: James Harkins <jamshark70@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Emacs-orgmode@gnu.org
Subject: Re: org-mobile-push vs. symlinks
Date: Mon, 7 Jan 2013 10:34:08 +0800 [thread overview]
Message-ID: <CAFniQ7Vmg2bCUYeCSxCfn8x154ZyHc9Mz1292YSzywG9=OYM6Q@mail.gmail.com> (raw)
In-Reply-To: <87sj6efm7q.fsf@bzg.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
On Jan 6, 2013 9:57 PM, "Bastien" <bzg@altern.org> wrote:
>
> Hi James,
>
> James Harkins <jamshark70@gmail.com> writes:
>
> > I'm not sure of the procedure to contribute to the org manual, but I
> > might suggest something like this, under MobileOrg section B2:
>
> I added a footnote:
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=76684b5
(The thread that wouldn't die...)
I just looked at the footnote text... why did we go from "symlinks work if
the name is the same" to an unqualified "symlinks are not supported"?
It isn't always feasible, or even desirable in some cases, to keep all your
org files under org-directory. For instance, I have a separate project
folder for a series of concerts to be given in the spring. If I back up
this folder, I want the project's org file to come with it. The updated
documentation seems to suggest that I should store the org file physically
under org-directory and place a symlink under the project directory, making
backups a bit more complex ("oh my, I forgot again what is the cp or rsync
option to follow links... man page...").
I can accept the same-name requirement, but it really makes much more sense
to me to keep org files physically with their projects. So I'd kindly
request that future org-mobile changes avoid breaking the use of symlinks
in org-directory (which currently does work). Documenting that symlinks are
supported (with the one caveat about the filename) is a step in that
direction.
hjh
[-- Attachment #2: Type: text/html, Size: 1888 bytes --]
next prev parent reply other threads:[~2013-01-07 2:34 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 ` org-mobile-push vs. symlinks James Harkins
2012-12-15 8:49 ` 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFniQ7Vmg2bCUYeCSxCfn8x154ZyHc9Mz1292YSzywG9=OYM6Q@mail.gmail.com' \
--to=jamshark70@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=bzg@altern.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.