Re: [O] [bug] Partially disable interpretation of subscripts

2013-12-23 Thread Sebastien Vauban 
Hello Nicolas,

> "Sebastien Vauban" writes:
>> In order to be able to write names such as CODE_STATUT without STATUT
>> being written in subscript, I'm using the {} value for the ^ option.
>>
>> Though, doing so,
>>
>> - a_b is interpreted as subscript
>> - a_{b} is left as is
>>
>> In a way, the opposite of what I'm expecting.
>> Am I missing something?
>
> No, I forgot a `not' in a recent patch. This should now be fixed.

Confirmed!

> Thank you for reporting it.

Thank you for fixing quickly.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] [bug] Partially disable interpretation of subscripts

2013-12-20 Thread Nicolas Goaziou 


Hello,

"Sebastien Vauban" 
writes:

> In order to be able to write names such as CODE_STATUT without STATUT
> being written in subscript, I'm using the {} value for the ^ option.
>
> #+TITLE: ECM Subscript
> #+OPTIONS:   ^:{}
>
> * Underscores in text
>
> x_i + x^2 + x^{2} + x_{i}
>
> | Key  | Value |
> |--+---|
> | CODE_STATUT  | 1 |
> | CONTRAT\_DEBUT\_DATE | 2 |
> | CONTRAT_FIN_DATE | 3 |
>
> Though, doing so,
>
> - a_b is interpreted as subscript
> - a_{b} is left as is
>
> In a way, the opposite of what I'm expecting.
>
> Am I missing something?

No, I forgot a `not' in a recent patch. This should now be fixed.

Thank you for reporting it.


Regards,

-- 
Nicolas Goaziou