emacs-orgmode
[Top][All Lists]
Advanced

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

Re: [Orgmode] Should 'QUOTE' turn off in-buffer mark-up?


From: Carsten Dominik
Subject: Re: [Orgmode] Should 'QUOTE' turn off in-buffer mark-up?
Date: Tue, 2 Jun 2009 09:47:31 +0200


On Jun 1, 2009, at 11:38 PM, Daniel J. Sinder wrote:

I just cut-and-pasted a table from the IETF RTP RFC into orgmode as follows:

* QUOTE RTP Header Format
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |V=2|P|X|  CC   |M|     PT      |       sequence number         |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                           timestamp                           |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |           synchronization source (SSRC) identifier            |
 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
 |            contributing source (CSRC) identifiers             |
 |                             ....                              |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The orgmode markup rules make this a bit of a mess. Actually, at least the content is undisturbed here, but I've seen worse -- for example, an otherwise well formatted table in which the columns have phone numbers with country codes starting with '+'. This leads to strikeout marks that actually strike through the cell contents!

So, would it make sense to turn off in-buffer markup under headings marked with the QUOTE keyword? Of course, prefixing every line with ':' has the desired effect, so there is an existing work-around, but requiring the prefix seems to make 'QUOTE' not very powerful/useful.

Indeed, QUOTE is useless and therefore has been removed from the docs.


(I can't find 'QUOTE' in the documentation now, so maybe this feature has been deprecated? But, #+BEGIN/END_EXAMPLE has the same problem.)

Not anymore.

- Carsten





reply via email to

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