Great! I'd think that shall do.
Thank you for this fast fix!
On 2016-08-23 Tue 07:44, Nicolas Goaziou wrote:
> Hello,
>
> John Kitchin 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
>> activ
Hello,
John Kitchin 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
Thank you for this confirmation of the abbreviation issue.
> I would suggest just defining short links ;)
Well, there are limits to this approach e.g. file+mnl {mnl = myNewLink}.
Furthermore, link definitions then tend to become pretty cryptic :-(.
Optimally, the 'org-link-abbrev-alist' could (
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
Yes, with pleasure:
Let's put it the most simple way:
1. Here is my new-link definition:
#+begin_src emacs-lisp
(org-link-set-parameters "new-link" :help-echo "show new-link's help echo")
#+end_src
(it doesn't change matter, if there would be :follow or :store function etc.)
2. the 'toolti
that isn't a feature I have used too often. Could you post a small example
that illustrates the problem? Thanks,
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@john
The new link parameters are fabulous!
Only the parameter ':help-echo' seems not to be respected, if a link is used by
an abbreviated form as defined by the 'org-link-abbrev-alist'.
Would be nice, if this could be fixed.
Anyway, thank you for this big step forward,
mc
smime.p7s
Description: S/M
