From: Philipp Kroos <Philipp.Kroos@t-online.de>
To: emacs-orgmode@gnu.org
Subject: Re: add entries to *emphasis-alist
Date: Sun, 19 Aug 2012 14:53:09 +0200 [thread overview]
Message-ID: <20120819125309.GA14590@Vostro> (raw)
In-Reply-To: <87vcgfm7rx.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
Well, sorry..
Before sending the mail I read the documentation on
http://orgmode.org/worg/org-contribute.html#sec-4
regarding correct submission of patches... and did it wrong.
So just for the records, here it is again.
Hopefully, if I can contribute a `real' patch someday, the format will
be right ;)
Regards, philipp
On Sun, Aug 19, 2012 at 01:38:10PM +0200, Nicolas Goaziou wrote:
> Hello,
>
> Philipp Kroos <Philipp.Kroos@t-online.de> writes:
>
> > 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
> > already defined.
> > It might be of minor interest, anyway, I've attached a patch-suggestion
> > that would clearify the usage sufficiently, at least for me...
>
> At some point, emphasis markers will be hard-coded anyway. Though, it
> will be easy to change their meaning during the export process.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: 0001-Minor-change-of-documentation.patch --]
[-- Type: text/plain, Size: 1289 bytes --]
From 6bd616854ccb981693c2178c5a9c0378cf3954aa Mon Sep 17 00:00:00 2001
From: Philipp Kroos <Philipp.Kroos@t-online.de>
Date: Sun, 19 Aug 2012 14:34:56 +0200
Subject: [PATCH] Minor change of documentation
* lisp/org.el org-emphasis-alist: Clearified the documentation
The value is not changeable with a setq-form, the
customization-interface should be used. The change describes that.
TINYCHANGE
---
lisp/org.el | 4 +++-
1 Datei geändert, 3 Zeilen hinzugefügt(+), 1 Zeile entfernt(-)
diff --git a/lisp/org.el b/lisp/org.el
index 3bf338d..c70d94d 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -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'."
:group 'org-appearance
:set 'org-set-emph-re
:type '(repeat
--
1.7.11.4
next prev parent reply other threads:[~2012-08-19 12:57 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
2012-08-19 11:38 ` Nicolas Goaziou
2012-08-19 12:53 ` Philipp Kroos [this message]
2012-08-19 15:25 ` Bastien
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=20120819125309.GA14590@Vostro \
--to=philipp.kroos@t-online.de \
--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).