From: Philipp Kroos <Philipp.Kroos@t-online.de>
Subject: Re: add entries to *emphasis-alist
Date: Sun, 19 Aug 2012 13:01:10 +0200 [thread overview]
Message-ID: <20120819110109.GA6210@Vostro> (raw)
[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]
It worked using customize, thanks. And thanks for the explanation, Nick.
At least my approach to set the value would not work at all without an
explicit call to org-set-emph-re, since it relied on the variable being
It might be of minor interest, anyway, I've attached a patch-suggestion
that would clearify the usage sufficiently, at least for me...
Best regards, Philipp
On Fri, Aug 17, 2012 at 03:50:35PM -0400, Nick Dokos wrote:
> Sebastien Vauban <firstname.lastname@example.org> wrote:
> > You have to make that customization *before* loading Org in your .emacs file.
> > Weird, never really understood why, but that's like that.
> The point is that the value of org-emphasis-alist (as well as the value
> of org-emphasis-regexp-components) is used in order to calculate the
> value of org-emph-re by calling the function org-set-emph-re afterwards:
> it's org-emph-re that's used for the all the gory calculations, not
> org-emphasis-alist, which just provides a nicer interface.
> So if you arrange to call the org-set-emph-re function afterwards, you
> can change org-emphasis-alist at any time. Customize makes it easy, in
> that it does that automatically (see the :set property
> of org-emphasis-alist).
> If you do the setq before loading org, then what happens is that when the
> defcustom is encountered, the value of the :set property (a function) is
> called: the modified value of org-emphasis-alist is then used to calculate
> org-emph-re, instead of the original default. If you do it after, none
> of that happens and it's as if you never changed it.
> PS BTW, the docstring for the variable says: "Use customize to modify
> this, or restart Emacs after changing it" but I'm not sure that's
> correct: if you change the variable in one session, the value is not
> going to be propagated to the next session, unless you use customize
> or put the setq in .emacs. In the latter case, it's not going to work
> unless you do it the way Seb describes: set it before loading Org.
> So restarting emacs is *not* enough. Am I missing something?
[-- Attachment #2: org-emphasis-alist-doc.patch --]
[-- Type: text/plain, Size: 753 bytes --]
diff --git a/lisp/org.el b/lisp/org.el
index 3bf338d..c70d94d 100644
@@ -3770,7 +3770,9 @@ characters, the face to be used by font-lock for highlighting in Org-mode
Emacs buffers, and the HTML tags to be used for this.
For LaTeX export, see the variable `org-export-latex-emphasis-alist'.
For DocBook export, see the variable `org-export-docbook-emphasis-alist'.
-Use customize to modify this, or restart Emacs after changing it."
+The value of org-emphasis-alist is used to calculate a regular expression
+during startup; changing it manually may not have an effect.
+You should use customize to modify this. Otherwise, see `org-set-emph-re'."
next prev parent reply other threads:[~2012-08-19 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 12:26 add entries to *emphasis-alist Philipp Kroos
2012-08-17 19:01 ` Sebastien Vauban
2012-08-17 19:50 ` Nick Dokos
2012-08-19 11:01 ` Philipp Kroos [this message]
2012-08-19 11:38 ` Nicolas Goaziou
2012-08-19 12:53 ` Philipp Kroos
2012-08-19 15:25 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).