emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: mc <mc@aiguphonie.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: new link parameters and link abbreviations
Date: Sat, 20 Aug 2016 17:55:03 +0300	[thread overview]
Message-ID: <8861C3F7-1B34-4752-9935-1F0ED80136A2@aiguphonie.com> (raw)
In-Reply-To: <CAJ51ETrF=HLqpzUS0L9PiHX5-jMD0TdANJExdz+XXLo80nCD6Q@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1668 bytes --]

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 'tooltip' shows my :help-echo string as expected.

[[new-link:awesome]]


3. Then I add the following abbreviation of the above link:

#+begin_src emacs-lisp
  (setq org-link-abbrev-alist '(("nl" . "new-link::%s")))
#+end_src


4. the 'tooltip' does not work but shows the default:

[[nl:awesome]]


Hope that clarifies the issue.


Thanks once more for your sustained patience making link handling much
easier and more powerful!
mc



> On 20 Aug 2016, at 17:17, John Kitchin <jkitchin@andrew.cmu.edu> wrote:
> 
> 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
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu <http://kitchingroup.cheme.cmu.edu/>
> 
> 
> On Fri, Aug 19, 2016 at 12:13 AM, mc <mc@aiguphonie.com <mailto:mc@aiguphonie.com>> wrote:
> 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
> 


[-- Attachment #1.2: Type: text/html, Size: 3820 bytes --]

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2667 bytes --]

  reply	other threads:[~2016-08-20 14:55 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 [this message]
2016-08-23  1:03       ` John Kitchin
2016-08-23  6:25         ` Martin Carlé
2016-08-23  7:44         ` Nicolas Goaziou
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=8861C3F7-1B34-4752-9935-1F0ED80136A2@aiguphonie.com \
    --to=mc@aiguphonie.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /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).