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: Fri, 14 Jan 2022 10:19:33 +0800 [thread overview]
Message-ID: <878rvj5aa2.fsf@localhost> (raw)
In-Reply-To: <80a6g09j29.fsf@felesatra.moe>
Allen Li <darkfeline@felesatra.moe> writes:
>> I agree. The question is whether changing to
>> (defvar org-id-link-to-org-use-id)
>> solves your problem.
>
> Thanks for your concern. By editing ob-tangle.el, I can confirm that
> changing this does solve my problem.
>
> If I must, I could provide a reproducible example, but I feel like
> that costs unnecessary effort on the part of everyone involved if we
> agree on the above point.
Let me clarify what I am worrying about.
We have 132 occurrences of (defvar foo nil) in the code.
I am genuinely surprised that changing defvar fixed the problem for you
and at the same time nobody reported similar issues with the other 131
defvars. That's why I really want to get a reproducer and understand
what is going on there. So far, I don't understand how defvar can break
anything except in case of some strange compilation/mixed installation
problems.
Best,
Ihor
next prev parent reply other threads:[~2022-01-14 2:16 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
2022-01-13 7:43 ` Allen Li
2022-01-14 2:19 ` Ihor Radchenko [this message]
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=878rvj5aa2.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).