From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [texinfo] Info links
Date: Mon, 25 Feb 2013 10:29:28 -0500 [thread overview]
Message-ID: <CAEWDx5dzmaKe7ATumgKDV7AWr1UGtk2uPRcj7J5v4Fu318T=Xw@mail.gmail.com> (raw)
In-Reply-To: <m1y5eh1c5l.fsf@poto.myhome.westell.com>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
Hello Tom.
On 21 February 2013 18:26, Thomas S. Dye <tsd@tsdye.com> wrote:
> Hi Jon,
>
> Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
>
> > Hello Tom,
> >
> > On 21 February 2013 15:09, Thomas S. Dye <tsd@tsdye.com> wrote:
> >
> >> Aloha all,
> >>
> >> This link (which works correctly in the Org mode buffer):
> >>
> >> [[info:emacs#Indirect Buffers][GNU Emacs Manual]]
> >>
> >> exports to texinfo like this:
> >>
> >> @ref{top,GNU Emacs Manual,,emacs#Indirect Buffers,}
> >>
> >> when I was hoping to approximate this:
> >>
> >> @ref{Indirect Buffers,,,emacs,GNU Emacs Manual}
> >>
> >> Is this a bug, or should I be doing something differently?
> >>
> >> This was an oversight by me. I only set ':' as the splitter in the
> path.
> > I'm not at the machine that has the right SSH key to be able to push
> > the fix, however if you change the # to : it should export properly (I'll
> > add # as a marker to split on as well once I'm at the right machine).
> >
> > This will also work properly in Org to access the correct node.
>
> Yes, the : works fine everywhere. Thanks!
>
I've added support for both # and : in info links. So now it should
work either way.
Regards,
--
Jon
> All the best,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>
[-- Attachment #2: Type: text/html, Size: 2225 bytes --]
prev parent reply other threads:[~2013-02-25 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 20:09 [texinfo] Info links Thomas S. Dye
2013-02-21 23:03 ` Jonathan Leech-Pepin
2013-02-21 23:26 ` Thomas S. Dye
2013-02-25 15:29 ` Jonathan Leech-Pepin [this message]
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='CAEWDx5dzmaKe7ATumgKDV7AWr1UGtk2uPRcj7J5v4Fu318T=Xw@mail.gmail.com' \
--to=jonathan.leechpepin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
/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).