[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: On being web-friendly and why info must die

From: Achim Gratz
Subject: Re: On being web-friendly and why info must die
Date: Wed, 17 Dec 2014 18:55:45 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

Richard Stallman writes:
>   > The simple markup is *bold*, =verbatim=, ~code~, /italic/
>   > +strike-through+ and _underline_.  The actual rules are a bit more
>   > complicated since some of that is costumizable for historical reasons.
> Here's one way it could be done:
> //emph//
> /=dfn=/
> ==code==
> '=samp='
> .=file=.
> _kbd_
> *strong*
> @variable@
> (We don't need strike-through or underline.)

Org uses regex parsing for most of this stuff, so good performance very
much requires that you don't need to backtrack often.  These suggestions
would work for proper (tokenized) parsing, but are most likely not
acceptable for Org (something like this has been tried before I should

Besides, I don't really think that this suggestion fulfills the goal of
having easily discernible semantic markup.  It's deeply magical, awkward
to type in some keyboard layouts and hard to read in a variety of fonts.
I guess that a lot of contributors would simply cargo-cult this markup
into the documentation without ever knowing what they are doing.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]