From: 8dcc <8dcc.git@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Can't export variable named "nil" to Texinfo
Date: Wed, 09 Oct 2024 19:19:43 +0200 [thread overview]
Message-ID: <87plo98a8g.fsf@gmail.com> (raw)
In-Reply-To: <877cahnu3i.fsf@localhost> (message from Ihor Radchenko on Wed, 09 Oct 2024 16:01:37 +0000)
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
Ihor Radchenko <yantar92@posteo.net> 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 "combining attributes", but I guess that
makes sense.
> In theory, we may fix this edge case just for ox-texinfo. But is it
> worth it?
I am not sure if it's worth fixing, specially since I don't know any
possible alternatives apart from using another keyword for specifying
this "attribute combination" (again, not sure how that works). Either
way, modifying existing behavior doesn't sound too good to me, specially
considering the amount of "nil" variables :)
> 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
how `nil' works, and when it's used.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2024-10-09 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-28 15:08 [BUG] Can't export variable named "nil" to Texinfo 8dcc
2024-10-09 16:01 ` Ihor Radchenko
2024-10-09 17:19 ` 8dcc [this message]
2024-10-14 18:43 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87plo98a8g.fsf@gmail.com \
--to=8dcc.git@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).