* Should 'QUOTE' turn off in-buffer mark-up?
@ 2009-06-01 21:38 Daniel J. Sinder
2009-06-02 7:47 ` Carsten Dominik
0 siblings, 1 reply; 2+ messages in thread
From: Daniel J. Sinder @ 2009-06-01 21:38 UTC (permalink / raw)
To: org-mode
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.
(I can't find 'QUOTE' in the documentation now, so maybe this feature
has been deprecated? But, #+BEGIN/END_EXAMPLE has the same problem.)
Dan
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Should 'QUOTE' turn off in-buffer mark-up?
2009-06-01 21:38 Should 'QUOTE' turn off in-buffer mark-up? Daniel J. Sinder
@ 2009-06-02 7:47 ` Carsten Dominik
0 siblings, 0 replies; 2+ messages in thread
From: Carsten Dominik @ 2009-06-02 7:47 UTC (permalink / raw)
To: Daniel J. Sinder; +Cc: org-mode
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-06-02 7:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-06-01 21:38 Should 'QUOTE' turn off in-buffer mark-up? Daniel J. Sinder
2009-06-02 7:47 ` Carsten Dominik
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).