Hello,
Aaron Ecay writes:
> 2013ko abenudak 17an, Nicolas Goaziou-ek idatzi zuen:
>> The more I look at it, the more I'm inclined to think that it's totally
>> useless. I don't think anyone wants tables removed from Org syntax.
>>
>> Though, occasionally some line starting with "|" can be inter
2013ko abenudak 17an, Nicolas Goaziou-ek idatzi zuen:
> The more I look at it, the more I'm inclined to think that it's totally
> useless. I don't think anyone wants tables removed from Org syntax.
>
> Though, occasionally some line starting with "|" can be interpreted as
> a table. In this case,
Nicolas Goaziou writes:
> Hello,
>
> Aaron Ecay writes:
>
>> 1) In exporting the following org buffer to latex, I get the following
>> stack trace (at end of email because of length):
>>
>> =
>> #+options: |:nil
>>
>> | foo | bar |
>> =
>
> The more I look at it, the more I'm inclined to
Hello,
Aaron Ecay writes:
> 1) In exporting the following org buffer to latex, I get the following
> stack trace (at end of email because of length):
>
> =
> #+options: |:nil
>
> | foo | bar |
> =
The more I look at it, the more I'm inclined to think that it's totally
useless. I don't t
Hello,
1) In exporting the following org buffer to latex, I get the following
stack trace (at end of email because of length):
=
#+options: |:nil
| foo | bar |
=
2) When exporting the following buffer to latex:
=
#+options: ^:nil
foo_{*bar*}
=
I get (ignoring document preambl
