From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: c-font-lock-extra-types and friends
Date: Sat, 18 Mar 2023 11:35:10 +0200 [thread overview]
Message-ID: <83ttyibdwx.fsf@gnu.org> (raw)
In-Reply-To: <ZBWBDkqrnqyP7e+0@ACM> (message from Alan Mackenzie on Sat, 18 Mar 2023 09:14:54 +0000)
> Date: Sat, 18 Mar 2023 09:14:54 +0000
> Cc: emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> On Sat, Mar 18, 2023 at 08:40:38 +0200, Eli Zaretskii wrote:
> > Ping!
>
> Sorry, I got bogged down with something else, the last few days.
>
> > Alan, with the pretest of Emacs 29 very near, I'd like to resolve
> > this issue. TIA.
>
> OK, I'll backport it to Emacs 29.
Great, thanks.
> > > . why did you add a new function c-list-of-strings, when we already
> > > had c-string-list-p there?
> > > . any reason not to backport this to the emacs-29 branch?
>
> I'd forgotten about c-string-list. How did you pick up the duplication,
> just as a matter of interest?
I knew about it before I asked the original question about
c-font-lock-extra-types: I've seen that you use c-string-list for
other variables. I expected you to use it for those I complained
about, and was surprised to see that you invented a new function,
basically identical to that one.
> I'll get rid of c-list-of-strings.
Thanks.
> I'm working on this now. Hopefully everything will be resolved today.
Great.
prev parent reply other threads:[~2023-03-18 9:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 6:57 c-font-lock-extra-types and friends Eli Zaretskii
2023-03-06 12:27 ` Alan Mackenzie
2023-03-09 9:47 ` Francesco Potortì
2023-03-13 16:54 ` Alan Mackenzie
2023-03-13 17:12 ` Eli Zaretskii
2023-03-13 18:04 ` Alan Mackenzie
2023-03-13 18:37 ` Alan Mackenzie
2023-03-14 12:25 ` Eli Zaretskii
2023-03-14 19:51 ` Eli Zaretskii
2023-03-18 6:40 ` Eli Zaretskii
2023-03-18 9:14 ` Alan Mackenzie
2023-03-18 9:35 ` Eli Zaretskii [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ttyibdwx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@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.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).