From: Allen Li <firstname.lastname@example.org> To: Ihor Radchenko <email@example.com> Cc: firstname.lastname@example.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: Mon, 24 Jan 2022 21:20:30 -0800 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <871r19ryxb.fsf@localhost> (Ihor Radchenko's message of "Sat, 15 Jan 2022 20:00:48 +0800") Ihor Radchenko <firstname.lastname@example.org> writes: > Unfortunately, fixing the occurrences of (defvar foo nil) is not > completely straightforward. Some of them are real defvars. I see, I thought you meant those defvars were also used for dynamic scoping. > > If someone is willing to check all the occurrences of > (defvar +[^ ]+ +nil) and remove nil values where we merely put a defvar > to silence byte-compiler, please do it. My initial request was just to fix this one instance that is actively troubling me. If there are any other known cases of defvar, they should also be fixed. If not, then let's wait until someone identifies them. If any maintainers reading this could fix this one defvar, that'd be great. > > Also, I feel that my Elisp-foo is not good enough in this specific > scenario. I invite others to reply if they feel that changing > (defvar foo nil) to (defvar foo) for externally defined variables is > _not_ universally safe. > > Best, > Ihor
next prev parent reply other threads:[~2022-01-25 5:22 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-11 11:03 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 2022-01-14 9:50 ` Allen Li 2022-01-15 12:00 ` Ihor Radchenko 2022-01-25 5:20 ` Allen Li [this message] 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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/)]' \ /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
Code repositories for project(s) associated with this 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).