From: Ihor Radchenko <yantar92@gmail.com>
To: Allen Li <darkfeline@felesatra.moe>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] ob-tangle overrides user customization of org-id-link-to-org-use-id [9.5.2 (9.5.2-gfbff08 @ /home/ionasal/.emacs.d/elpa/org-9.5.2/)]
Date: Wed, 12 Jan 2022 22:41:53 +0800 [thread overview]
Message-ID: <877db5ow26.fsf@localhost> (raw)
In-Reply-To: <80v8yqkssa.fsf@felesatra.moe>
Allen Li <darkfeline@felesatra.moe> writes:
>> Allen Li <darkfeline@felesatra.moe> writes:
>>
>>> In ob-tangle.el, the line
>>>
>>> (defvar org-id-link-to-org-use-id nil) ; Dynamically scoped
>>>
>>> appears to override the user's customization of
>>> org-id-link-to-org-use-id.
>>
>> Have you seen this happening?
>
> Yes, that's why I filed the bug.
If you saw this, then the root cause is probably not in defvar.
Are you able to provide a reproducer?
>> defvar only matters if the variable is not yet defined:
>> bar ;; => error void-variable
>> (defvar bar 'value) ;; bar = 'value
>
> Yes, that is so.
>
> Even if org-id-link-to-org-use-id were always set at this point, there
> would be no reason to use
>
> (defvar org-id-link-to-org-use-id nil)
>
> instead of
>
> (defvar org-id-link-to-org-use-id)
I agree. The question is whether changing to
(defvar org-id-link-to-org-use-id)
solves your problem.
Best,
Ihor
next prev parent reply other threads:[~2022-01-12 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 11:03 [BUG] ob-tangle overrides user customization of org-id-link-to-org-use-id [9.5.2 (9.5.2-gfbff08 @ /home/ionasal/.emacs.d/elpa/org-9.5.2/)] Allen Li
2022-01-11 11:42 ` Ihor Radchenko
2022-01-11 18:53 ` Allen Li
2022-01-12 14:41 ` Ihor Radchenko [this message]
2022-01-13 7:43 ` Allen Li
2022-01-14 2:19 ` Ihor Radchenko
2022-01-14 9:50 ` Allen Li
2022-01-15 12:00 ` Ihor Radchenko
2022-01-25 5:20 ` Allen Li
2022-01-30 8:56 ` 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=877db5ow26.fsf@localhost \
--to=yantar92@gmail.com \
--cc=darkfeline@felesatra.moe \
--cc=emacs-orgmode@gnu.org \
/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).