From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [Out-of-Thread] Re: [RFC] Org syntax (draft)
Date: Mon, 18 Mar 2013 22:24:37 +0100 [thread overview]
Message-ID: <87ppywpfje.fsf@pank.eu> (raw)
In-Reply-To: B72CDC2B-72F6-43A8-AC70-E6E6295766EC@gmail.com
Carsten Dominik <carsten.dominik@gmail.com> writes:
> The reason why the emphasis regexp components were made configurable
> in the first place is because when the feature was introduced, I had
> no idea what would work, and I redesigned this part several times
> over. Emphasis is a very heuristic system, the character that are
> allowed before and after the markers are necessarily a compromise, and
> we will always find people for who the chosen selection will not work.
> That is why I would like to argue for keeping this part hackable, even
> if I agree that the official definition should be fixed. Keeping this
> variable a customize variable invites changes also by people who do
> not really know what they are doing. Turning it into a defvar or
> defconst and somewhere document how to hack around the restriction if
> you really need to sounds like a good solution for me.
To some extend I disagree, I think. Well, a contrib library is of
course OK, but I think it's not the right way to go about it. . .
Would it be possible to make it easier to make 'custom' highlights?
In a previous thread a [cite:key] syntax was suggested. Perhaps, a
better way for custom emphasis would be [type:value] allowing for
custom functions for each type. E.g. [TYPE:value] would run function
a function org-type-keys-TYPE which returns value formatted with a
special face.
Perhaps this is more cumbersome and perhaps it is no more 'structured'
than using customized emphases.
–Rasmus
--
El Rey ha muerto. ¡Larga vida al Rey!
next prev parent reply other threads:[~2013-03-18 21:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 23:02 [Out-of-Thread] Re: [RFC] Org syntax (draft) zeltak
2013-03-18 6:08 ` Carsten Dominik
2013-03-18 10:48 ` Thorsten Jolitz
2013-03-18 13:33 ` zeltak
2013-03-18 15:21 ` W. Greenhouse
2013-03-18 16:05 ` Marcin Borkowski
2013-03-18 19:19 ` Carsten Dominik
2013-03-18 21:24 ` Rasmus [this message]
2013-03-19 3:47 ` Aaron Ecay
2013-03-19 9:49 ` Nicolas Richard
2013-03-21 21:36 ` Nicolas Goaziou
2013-04-12 6:23 ` Bastien
2013-04-12 6:23 ` Bastien
2013-03-19 4:07 ` Samuel Wales
-- strict thread matches above, loose matches on Subject: below --
2013-03-20 17:47 zeltak
2013-03-07 20:37 Nicolas Goaziou
2013-03-09 23:16 ` Achim Gratz
2013-03-09 23:49 ` Nicolas Goaziou
2013-03-10 4:35 ` Jambunathan K
2013-03-10 7:08 ` Nicolas Goaziou
2013-03-10 10:14 ` Bastien
2013-03-10 15:44 ` Jambunathan K
2013-03-14 16:58 ` Eric S Fraga
2013-03-14 18:26 ` Jambunathan K
2013-03-14 18:51 ` David Engster
2013-03-14 19:03 ` [Out-of-Thread] " Jambunathan K
2013-03-14 19:15 ` David Engster
2013-03-14 19:23 ` Jambunathan K
2013-03-14 19:29 ` David Engster
2013-03-14 19:52 ` Jambunathan K
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=87ppywpfje.fsf@pank.eu \
--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).