Re: [O] Quoting characters?

2012-01-20 Thread Samuel Wales
No solution, but sympathy.  Syntax risk is difficult to prevent in Org
 I wonder if we can come up with incremental improvements that involve
more universal escaping, quoting, nesting, etc. mechanisms somehow?

(This is /not/ intended to be a sly plug for my universal syntax
proposal.  That's not intended to replace all existing syntax, but
only to be used for future syntax.  However, I do have a list of
parsing risk issues on the list someplace that might be a reference.)

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
===
Bigotry against people with serious diseases is still bigotry.



[O] Quoting characters?

2012-01-12 Thread Yu
Hello!

When working with Org-mode I sometimes run into oddities, when a
character I need clashes with org-mode syntax. Is there a way to avoid
this?

Examples would be:

Writing a macro that expands to `$\neg$':
#+macro: not $\neg$
expands to
$
eg$
even if I write it as \\neg. Writing the macro in the C-c C-' buffer
produces \n, but when editing it again, it is displayed as a newline.

Similiarily, I found no way to have "\^" or "\_" appear in the export,
when I wanted to write about escaping ^ and _ as =\^= and =\_=
respectively. Here as well, writing multiple backslashes wouldn't
change the output.


Maybe related, I found that when editing an block
: #+foo: bar
: This is an org-mode example
with C-c C-', the result text will be
: ,#+foo: bar
: This is an org-mode example
The extra comma generated will still be there also in the C-c C-'
editing buffer.

In a source code block, that is declared to be of the language "org",
this behaviour doesn't appear, but it reappears for other languages.

When exporting to html or pdf, the comma isn't present for "src"
blocks, but it is for the "colon" blocks.


kind regards, Yu