From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>, mc <mc@aiguphonie.com>
Subject: Re: new link parameters and link abbreviations
Date: Tue, 23 Aug 2016 09:44:48 +0200 [thread overview]
Message-ID: <87vaysudxr.fsf@saiph.selenimh> (raw)
In-Reply-To: <m2fupws3cw.fsf@Johns-MacBook-Air.local> (John Kitchin's message of "Mon, 22 Aug 2016 21:03:59 -0400")
Hello,
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> I can confirm this happens. I think it happens because the abbreviation
> is not listed in org-plain-link-re, so when the bracket link is
> activated, no type is ever defined (it is done by a group in the
> org-plain-link-re). The type is somewhat fundamental to the activation
> function, as it is used to look up all the link properties, and hence
> you get the default help (and all other properties too).
>
> I haven't thought of a simple fix though. It would involve adding the
> abbreviations to the known link types, and some kind of lookup for when
> the type in a link is not in org-link-parameters that resolves the type
> to something in org-link-parameters. Since the abbreviations seem to
> have quite flexible format, it isn't obvious how to do that robustly,
> without changing the abbreviation syntax.
I pushed a simple fix as 112463cbffb8bec7ec318c27d3b862e9ddcf76f3 that
avoids extending `org-plain-link-re'. Link abbreviation is limited to
bracket links whereas `org-link-parameters' helps defining plain links.
Let me know if it isn't a sufficient solution.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-08-23 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1a8g992vh.fsf@aiguphonie.com>
2016-08-19 4:13 ` new link parameters and link abbreviations mc
2016-08-20 14:17 ` John Kitchin
2016-08-20 14:55 ` mc
2016-08-23 1:03 ` John Kitchin
2016-08-23 6:25 ` Martin Carlé
2016-08-23 7:44 ` Nicolas Goaziou [this message]
2016-08-23 9:20 ` Martin Carlé
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=87vaysudxr.fsf@saiph.selenimh \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=mc@aiguphonie.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).