From: Kaushal Modi <email@example.com> To: Kaushal Modi <firstname.lastname@example.org>, Emmanuel Charpentier <email@example.com>, firstname.lastname@example.org, emacs-org list <email@example.com> Subject: Re: [PATCH] c-csl : accept relative CSL filenames Date: Fri, 18 Feb 2022 14:17:52 -0500 [thread overview] Message-ID: <CAFyQvY1_cQw4=KPdE0Q6spavJ+Ehs+CvAt8S7kOpe-sD2Bpycg@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> > It is already in the main branch, AFAIU. I assume you mean it should be > back-ported to bugfix branch. If that's the case, I don't know. This is > a new feature, and not a critical one: there are workarounds, as you > found out. Yes, sorry, I meant the bugfix branch. > This should be available when Org 9.6 is released. I don't know when > that will happen. OK. It's not urgent. I can wait. > I don't think Glenn Morris suggests using #'string-or-null-p, which > would contradict his statement. He is pointing out that ":safe > #'string-or-null-p" is better than ":safe t", even though but allowing > arbitrary locations (strings in this case) is not safe anyway. OK, I thought he referred to ":safe t" equivalent to any arbitrary location. I don't understand how ":safe #'string-or-null-p" can be potentially unsafe. So I will go by your judgment. So, no action needed. Thanks! :)
next prev parent reply other threads:[~2022-02-18 19:25 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-05 17:56 Emmanuel Charpentier 2021-11-19 12:54 ` Nicolas Goaziou 2021-11-19 18:10 ` M. ‘quintus’ Gülker 2021-12-10 9:20 ` Nicolas Goaziou 2022-02-18 14:51 ` Kaushal Modi 2022-02-18 18:16 ` Nicolas Goaziou 2022-02-18 19:17 ` Kaushal Modi [this message] -- strict thread matches above, loose matches on Subject: below -- 2021-10-19 18:24 Emmanuel Charpentier 2021-11-03 16:19 ` Nicolas Goaziou 2021-11-04 16:25 ` Emmanuel Charpentier 2021-11-04 22:16 ` Nicolas Goaziou 2021-11-04 22:36 ` Bruce D'Arcus 2021-11-05 12:18 ` Eric S Fraga 2021-11-05 9:38 ` M. ‘quintus’ Gülker
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='CAFyQvY1_cQw4=KPdE0Q6spavJ+Ehs+CvAt8S7kOpe-sD2Bpycg@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] c-csl : accept relative CSL filenames' \ /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).