From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: 71379@debbugs.gnu.org, schnoebelen.ph@gmail.com,
Eli Zaretskii <eliz@gnu.org>,
stefankangas@gmail.com
Subject: bug#71379: 29.3; Elisp compiler: warnings for formats given insufficiently many arguments
Date: Mon, 10 Jun 2024 16:27:53 +0200 [thread overview]
Message-ID: <A6254C08-8047-491F-B58A-F2309EDD1ECC@gmail.com> (raw)
In-Reply-To: <yp1o789kyid.fsf@fencepost.gnu.org>
10 juni 2024 kl. 10.11 skrev Andrea Corallo <acorallo@gnu.org>:
> But this is not local only already, see 'info-xref-output' and
> 'info-xref-output-error'.
Very much aware of that, and don't think it's worth doing anything about.
> There might be other occurencies outside
> emacs.git as well.
Already checked that as well, and there were almost none -- all I could find was a single occurrence in one package. Not that we really care since it's an internal and undocumented interface.
next prev parent reply other threads:[~2024-06-10 14:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 13:16 bug#71379: 29.3; Elisp compiler: warnings for formats given insufficiently many arguments Philippe Schnoebelen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-05 16:56 ` Mattias Engdegård
2024-06-05 17:48 ` Eli Zaretskii
2024-06-05 19:20 ` Mattias Engdegård
2024-06-06 4:38 ` Eli Zaretskii
2024-06-06 8:49 ` Mattias Engdegård
2024-06-06 23:22 ` Stefan Kangas
2024-06-07 6:21 ` Eli Zaretskii
2024-06-07 13:55 ` Andrea Corallo
2024-06-07 15:50 ` Eli Zaretskii
2024-06-08 18:15 ` Andrea Corallo
2024-06-08 18:18 ` Mattias Engdegård
2024-06-08 18:32 ` Eli Zaretskii
2024-06-09 13:57 ` Mattias Engdegård
2024-06-10 8:11 ` Andrea Corallo
2024-06-10 14:27 ` Mattias Engdegård [this message]
2024-06-10 21:14 ` Andrea Corallo
2024-06-11 14:30 ` Mattias Engdegård
2024-06-07 9:32 ` Mattias Engdegård
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=A6254C08-8047-491F-B58A-F2309EDD1ECC@gmail.com \
--to=mattias.engdegard@gmail.com \
--cc=71379@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=schnoebelen.ph@gmail.com \
--cc=stefankangas@gmail.com \
/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).