Dear org-mode list, Quick and easy question: I want to make a document that has a table where one column has variables and another column has descriptions. E.g. | VAR NAMES | DESC | |-----------+------------------------| | =var1= | this is the first var | | =var2= | this is the second var | | | | |-----------+------------------------| However, pressing [TAB] after writing =var1= causes #ERROR to show up. How do I make this work the way I am intending? :) Thanks, Stephen
On 31.3.2012, at 21:24, Stephen J. Barr wrote:
> Dear org-mode list,
>
> Quick and easy question:
>
> I want to make a document that has a table where one column has
> variables and another column has descriptions.
>
> E.g.
>
> | VAR NAMES | DESC |
> |-----------+------------------------|
> | =var1= | this is the first var |
> | =var2= | this is the second var |
> | | |
> |-----------+------------------------|
> However, pressing [TAB] after writing =var1= causes #ERROR to show up.
> How do I make this work the way I am intending? :)
| VAR NAMES | DESC |
|-----------+------------------------|
| ~var1~ | this is the first var |
| ~var2~ | this is the second var |
| | |
|-----------+------------------------|
- Carsten
Excellent. Thank you.
On Sat, Mar 31, 2012 at 3:47 PM, Carsten Dominik
<carsten.dominik@gmail.com> wrote:
>
> On 31.3.2012, at 21:24, Stephen J. Barr wrote:
>
>> Dear org-mode list,
>>
>> Quick and easy question:
>>
>> I want to make a document that has a table where one column has
>> variables and another column has descriptions.
>>
>> E.g.
>>
>> | VAR NAMES | DESC |
>> |-----------+------------------------|
>> | =var1= | this is the first var |
>> | =var2= | this is the second var |
>> | | |
>> |-----------+------------------------|
>> However, pressing [TAB] after writing =var1= causes #ERROR to show up.
>> How do I make this work the way I am intending? :)
>
>
> | VAR NAMES | DESC |
> |-----------+------------------------|
> | ~var1~ | this is the first var |
> | ~var2~ | this is the second var |
> | | |
> |-----------+------------------------|
>
> - Carsten
>
> On 31.3.2012, at 21:24, Stephen J. Barr wrote: >> I want to make a document that has a table where one column has >> variables and another column has descriptions. >> | VAR NAMES | DESC | >> |-----------+------------------------| >> | =var1= | this is the first var | >> | =var2= | this is the second var | >> | | | >> |-----------+------------------------| >> However, pressing [TAB] after writing =var1= causes #ERROR to show up. >> How do I make this work the way I am intending? :) Carsten Dominik <carsten.dominik@gmail.com> writes: > | VAR NAMES | DESC | > |-----------+------------------------| > | ~var1~ | this is the first var | > | ~var2~ | this is the second var | > | | | > |-----------+------------------------| Interesting, thanks. The manual says: Emphasis and monospace ---------------------- You can make words *bold*, /italic/, _underlined_, `=code=' and `~verbatim~', and, if you must, `+strike-through+'. Text in the code and verbatim string is not processed for Org mode specific syntax; it is exported verbatim. Is there any functional (or semantic?) difference between =code= and ~verbatim~? Could I use any to avoid escaping problems of the other? (A bit like ' versus " in some languages?) François
François Pinard <pinard@iro.umontreal.ca> writes: > Emphasis and monospace > ---------------------- > > You can make words *bold*, /italic/, _underlined_, `=code=' and > `~verbatim~', and, if you must, `+strike-through+'. Text in the code > and verbatim string is not processed for Org mode specific syntax; it > is exported verbatim. > > Is there any functional (or semantic?) difference between =code= and > ~verbatim~? For the current LaTeX exporter, Yes. > Could I use any to avoid escaping problems of the other? > (A bit like ' versus " in some languages?) This is =co%de=. This is ~verb%atim~. gets exported as This is \texttt{co\%de}. This is \verb~verb%atim~. HTH, -- Bastien
On Sat, Mar 31, 2012 at 9:24 PM, Stephen J. Barr <stephenjbarr@gmail.com> wrote: [...] > | =var1= | this is the first var | [...] > However, pressing [TAB] after writing =var1= causes #ERROR to show up. [...] Just for the records. This issue has been resolved in the meantime with: commit 8342fdb70aa28edbb7b0b18bf1f3c0fd2dd561fa Author: Bastien Guerry <bzg@altern.org> Date: Tue May 1 02:03:12 2012 +0200 It was also on my list of someday/maybe... Michael