From: tsd@tsdye.com (Thomas S. Dye)
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Links in #+caption: lines
Date: Wed, 03 Jun 2015 06:48:50 -1000 [thread overview]
Message-ID: <m2egls7n65.fsf@tsdye.com> (raw)
In-Reply-To: <87a8wh824p.fsf@gmx.us> (rasmus@gmx.us's message of "Wed, 03 Jun 2015 13:25:42 +0200")
Aloha Rasmus,
Rasmus <rasmus@gmx.us> writes:
> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> Aloha all,
>>
>> Links in #+caption: lines are shown as literal links. IIRC, they used
>> to show as descriptive links. Has this changed, or is my memory faulty?
>>
>> In any case, I'd like them to be descriptive links to keep the
>>
>> #+caption: lines as short as possible.
>
> Maybe it's an effect of 37d2a2d1cfa58c5334eec4f7fbabc4a2f313ab33? Cf.
>
> http://thread.gmane.org/gmane.emacs.orgmode/95415
>
> In any case, unless links can be fortified in captions, I think current
> behavior is OK. "Hidden" links are worse, IMO.
I don't know if it is an effect of 37d2a2d. I'm also seeing a different
background for captions, similar to the background the emacs 24 starter
kit gives me for #+begin_src and #+end_src lines.
I use links for citations, which frequently appear in captions when I
specify the source of data, etc. The paper I'm working on now looks a
bit ungainly in the Org mode buffer due to the literal links in captions
and the weird backgrounds.
If it is necessary to choose between literal links in macros or
descriptive links in captions, perhaps there could be a switch for users
like you and me who use one but not the other?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2015-06-03 16:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 6:08 Links in #+caption: lines Thomas S. Dye
2015-06-03 11:25 ` Rasmus
2015-06-03 16:48 ` Thomas S. Dye [this message]
2015-06-03 20:26 ` Rasmus
2015-06-05 0:05 ` Thomas S. Dye
2015-06-05 5:48 ` Rasmus
2015-06-05 6:57 ` Nicolas Goaziou
2015-06-05 8:41 ` Thomas S. Dye
2015-06-05 15:45 ` Rasmus
2015-06-09 7:22 ` Nicolas Goaziou
2015-06-09 17:18 ` Thomas S. Dye
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2egls7n65.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.