Hi James,
James Harkins writes:
> 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"?
Should be fixed now... thanks,
--
Bastien
James Harkins writes:
> 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"?
I overlooked the difference.
Please provide a patch.
~$ git clone git://orgmode.org/org-mode.git
~$ emacs &
C-x f org-mo
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/
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
Thanks!
--
Bastien
On Jan 4, 2013 11:34 PM, "Bastien" wrote:
>
> Hi James,
>
> James Harkins writes:
>
> > The outcome is the same as the first: document the issue.
>
> Org is yours :)
I worked in software support for awhile, so... I know what it means, e.g.,
when some behavior is labeled a "known issue" ;-)
I'm
Hi James,
James Harkins writes:
> The outcome is the same as the first: document the issue.
Org is yours :)
--
Bastien
On Jan 3, 2013 8:57 PM, "Bastien" wrote:
>
> Hi James,
>
> James Harkins writes:
>
> > - 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 sym
Hi James,
James Harkins writes:
> - 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
> pr
Hi David,
da...@adboyd.com (J. David Boyd) writes:
> How would we do that? Are there instructions somewhere on the proper
> way to create a patch file for this? The proper mode for diff? What
> has to be in a changelog?
>
> There are a few changes I'd like to see in mobile.el myself, and I'm
Bastien writes:
> James Harkins writes:
>
>> Anyway, I still don't understand the rationale for the current
>> behavior. Does anyone know why org-mobile-push resolves the agenda
>> files' names to symlink targets?
>
> The problem is that there is no active maintainer on org-mobile.el
> right no
James Harkins writes:
> Anyway, I still don't understand the rationale for the current
> behavior. Does anyone know why org-mobile-push resolves the agenda
> files' names to symlink targets?
The problem is that there is no active maintainer on org-mobile.el
right now... by default this is me,
Sorry for resending as a new thread. I had wanted to reply to my
original message on gmane, but gmane's search fails to locate the
thread (?).
Anyway, I still don't understand the rationale for the current
behavior. Does anyone know why org-mobile-push resolves the agenda
files' names to symlink t
12 matches
Mail list logo