8dcc <8dcc@gmail.com> writes:
>> Do you _really_ have variable name "nil"?
>
> Yes, I was not looking for this error, I didn't even know why it
> happened before you told me. I am using Org to write the manual for my
> Lisp interpreter, and I am exporting it to Texinfo. I wanted to explain
> h
Ihor Radchenko writes:
> It happens to be that :options nil is treated specially by Org
> export. "nil" is not read literally, but is instead interpreted as
> removing the option value - when one needs to combine multiple
> attributes and override previous setting.
I see. I didn't know about "co
8dcc <8dcc@gmail.com> writes:
> However, if the variable is named "nil" (without the quotes), the
> variable name is not exported, and a warning is generated when
> processing the .texi file:
>
> - Variable: nil ::
>
> Content...
>
> Results in:
>
> @defvar
> Content@dots{}
> @end
Hello,
I can export the following "Variable" to Texinfo with
`org-texinfo-export-to-texinfo':
- Variable: my-name ::
Content...
Results in the following .texi:
@defvar my-name
Content@dots{}
@end defvar
However, if the variable is named "nil" (without the quotes), the
variable nam
