From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Links in #+caption: lines
Date: Wed, 03 Jun 2015 22:26:56 +0200 [thread overview]
Message-ID: <87fv685yi7.fsf@gmx.us> (raw)
In-Reply-To: m2egls7n65.fsf@tsdye.com
Hi,
tsd@tsdye.com (Thomas S. Dye) writes:
> I don't know if it is an effect of 37d2a2d.
I just tested it against 50a0e712cceeef02c0d6a7c41b619b308ea1b15c.
37d2a2d seems critical here.
> 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.
On my computer with angry fruit colors, captions are formatted as
#+caption: caption text
AFC color Red Gray
Face org-meta-line org-block
I don't know starter kit. But the Leuven theme changes background colors
for various parts of Org like this:
https://github.com/fniessen/emacs-leuven-theme/blob/master/images/agenda-and-task-list.png
Is that your theme?
> 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.
For the latter try something like: (set-face-background 'org-block nil)
> 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?
In the patch I guess this is the passage you disagree with:
+ ((equal dc1 "+caption:")
+ (org-remove-flyspell-overlays-in (match-end 2) (match-end 0))
+ (remove-text-properties (match-beginning 0) (match-end 0)
+ '(display t invisible t intangible t))
+ (add-text-properties (match-beginning 1) (match-end 3)
+ '(font-lock-fontified t face org-meta-line))
+ (add-text-properties (match-beginning 6) (+ (match-end 6) 1)
+ '(font-lock-fontified t face org-block)))
Perhaps it is possible to let normal fontification rule in region six
above?
IMO hidden link (== no color highlight and not literal) is no good.
Rasmus
--
One thing that is clear: it's all down hill from here
next prev parent reply other threads:[~2015-06-03 20:27 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
2015-06-03 20:26 ` Rasmus [this message]
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
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=87fv685yi7.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
/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).