Re: [O] Superscripts and subscripts

2013-04-20 Thread Nicolas Goaziou
Hello, Christian Moe m...@christianmoe.com writes: Nicolas Goaziou writes: Of course, we could work around this with a new rule saying the longest match wins, which, in this case, is the underline. But it would be better to find a more elegant solution, one which would remove the sole

Re: [O] Superscripts and subscripts

2013-04-20 Thread Nicolas Goaziou
Hello, Achim Gratz strom...@nexgo.de writes: Nicolas Goaziou writes: Of course, we could work around this with a new rule saying the longest match wins, which, in this case, is the underline. But it would be better to find a more elegant solution, one which would remove the sole ambiguity,

Re: [O] Superscripts and subscripts

2013-04-19 Thread Nicolas Goaziou
Hello, Bastien b...@gnu.org writes: t...@tsdye.com (Thomas S. Dye) writes: With a recent git pull and #+OPTIONS: ^:{}, `C^{14}' is interpreted correctly but ` ^{14}C' is not, both in the Org buffer and in LaTeX export. The space before the caret appears to be the problem. Confirmed --

Re: [O] Superscripts and subscripts

2013-04-19 Thread Achim Gratz
Nicolas Goaziou writes: Of course, we could work around this with a new rule saying the longest match wins, which, in this case, is the underline. But it would be better to find a more elegant solution, one which would remove the sole ambiguity, AFAICT, in Org syntax. Suggestions welcome.

Re: [O] Superscripts and subscripts

2013-04-19 Thread Thomas S. Dye
Achim Gratz strom...@nexgo.de writes: Nicolas Goaziou writes: Of course, we could work around this with a new rule saying the longest match wins, which, in this case, is the underline. But it would be better to find a more elegant solution, one which would remove the sole ambiguity, AFAICT,

Re: [O] Superscripts and subscripts

2013-04-19 Thread Christian Moe
Nicolas Goaziou writes: Of course, we could work around this with a new rule saying the longest match wins, which, in this case, is the underline. But it would be better to find a more elegant solution, one which would remove the sole ambiguity, AFAICT, in Org syntax. How did this work

Re: [O] Superscripts and subscripts

2013-04-18 Thread Daniel Mahler
upgrading to trunk gives me the same behaviour as John reported, which, while not perfect, is better for tensors. On Wed, Apr 17, 2013 at 10:54 PM, Daniel Mahler dmah...@gmail.com wrote: In my .emacs I have (custom-set-variables ;;... '(org-pretty-entities t) '(org-use-sub-superscripts

Re: [O] Superscripts and subscripts

2013-04-17 Thread Daniel Mahler
This works for me in org 7.9.2 and emacs 24.1.1, but chaining as in 'x^{y}_{z}' will only fontify the ^{y} but not the _{z}, as I reported earlier today, but 'x^{y} _{z}' will fontify both, just with an ugly gap in the middle. cheers Daniel On Tue, Apr 16, 2013 at 1:29 AM, Bastien b...@gnu.org

Re: [O] Superscripts and subscripts

2013-04-17 Thread Daniel Mahler
In my .emacs I have (custom-set-variables ;;... '(org-pretty-entities t) '(org-use-sub-superscripts (quote {})) ;;... ) but I get the opposite result ' ^{14}C' works , but 'x^{y}_{z}' does not, On Wed, Apr 17, 2013 at 10:18 PM, John Hendy jw.he...@gmail.com wrote: On Wed, Apr 17, 2013 at

Re: [O] Superscripts and subscripts

2013-04-16 Thread Bastien
Hi Thomas, t...@tsdye.com (Thomas S. Dye) writes: With a recent git pull and #+OPTIONS: ^:{}, `C^{14}' is interpreted correctly but ` ^{14}C' is not, both in the Org buffer and in LaTeX export. The space before the caret appears to be the problem. Confirmed -- this was reported already once.

[O] Superscripts and subscripts

2013-04-15 Thread Thomas S. Dye
Aloha all, With a recent git pull and #+OPTIONS: ^:{}, `C^{14}' is interpreted correctly but ` ^{14}C' is not, both in the Org buffer and in LaTeX export. The space before the caret appears to be the problem. All the best, Tom -- Thomas S. Dye http://www.tsdye.com