From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Harkins Subject: Re: org-mobile-push vs. symlinks Date: Mon, 7 Jan 2013 10:34:08 +0800 Message-ID: References: <878v8abf1e.fsf@bzg.ath.cx> <874nixnerj.fsf@bzg.ath.cx> <87sj6efm7q.fsf@bzg.ath.cx> Reply-To: jamshark70@dewdrop-world.net Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=14dae93a156de776d904d2a9a954 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:52005) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ts2XT-0005wi-5w for Emacs-orgmode@gnu.org; Sun, 06 Jan 2013 21:34:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ts2XR-0002xi-Lv for Emacs-orgmode@gnu.org; Sun, 06 Jan 2013 21:34:11 -0500 Received: from mail-oa0-f52.google.com ([209.85.219.52]:57189) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ts2XR-0002xY-GQ for Emacs-orgmode@gnu.org; Sun, 06 Jan 2013 21:34:09 -0500 Received: by mail-oa0-f52.google.com with SMTP id o6so17375348oag.11 for ; Sun, 06 Jan 2013 18:34:08 -0800 (PST) In-Reply-To: <87sj6efm7q.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: Emacs-orgmode@gnu.org --14dae93a156de776d904d2a9a954 Content-Type: text/plain; charset=ISO-8859-1 On Jan 6, 2013 9:57 PM, "Bastien" wrote: > > Hi James, > > James Harkins 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 --14dae93a156de776d904d2a9a954 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Jan 6, 2013 9:57 PM, "Bastien" <bzg@altern.org> wrote:
>
> Hi James,
>
> James Harkins <jamshark70@g= mail.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=3D76684b5

(The thread that wouldn't die...)

I just looked at the footnote text... why did we go from &qu= ot;symlinks work if the name is the same" to an unqualified "syml= inks are not supported"?

It isn't always feasible, or even desirable in some case= s, to keep all your org files under org-directory. For instance, I have a s= eparate 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 fi= le physically under org-directory and place a symlink under the project dir= ectory, 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 us= e of symlinks in org-directory (which currently does work). Documenting tha= t symlinks are supported (with the one caveat about the filename) is a step= in that direction.

hjh

--14dae93a156de776d904d2a9a954--