From: "Mattias Engdegård" <mattiase@acm.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
65030@debbugs.gnu.org, eller.helmut@gmail.com,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#65030: 30.0.50; Check keyword args of make-process
Date: Tue, 8 Aug 2023 11:42:16 +0200 [thread overview]
Message-ID: <DFFD8575-17FF-4CFB-B333-66FA2AD42F9B@acm.org> (raw)
In-Reply-To: <87jzu5anpa.fsf@gmail.com>
8 aug. 2023 kl. 11.27 skrev Robert Pluim <rpluim@gmail.com>:
> You want to transform working code that passes ':coding-system' to
> `make-process' into code that signals an error?
That's probably a good idea (unless we are talking about a specific keyword that has to be ignored for compatibility), but I think we should start by improving existing errors.
However it should not preclude compile-time warnings of the kind proposed in the patch, which again can be applied more or less as-is.
next prev parent reply other threads:[~2023-08-08 9:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 6:47 bug#65030: 30.0.50; Check keyword args of make-process Helmut Eller
2023-08-05 9:21 ` Eli Zaretskii
2023-08-05 23:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-06 4:58 ` Eli Zaretskii
2023-08-06 8:49 ` Mattias Engdegård
2023-08-08 8:52 ` Robert Pluim
2023-08-08 9:16 ` Mattias Engdegård
2023-08-08 9:27 ` Robert Pluim
2023-08-08 9:42 ` Mattias Engdegård [this message]
2023-08-08 12:16 ` Eli Zaretskii
2023-08-08 13:05 ` Mattias Engdegård
2023-08-08 13:18 ` Robert Pluim
2023-08-08 16:38 ` Mattias Engdegård
2023-08-08 17:14 ` Helmut Eller
2023-08-08 20:15 ` Mattias Engdegård
2023-08-08 17:43 ` Eli Zaretskii
2023-08-08 17:51 ` Mattias Engdegård
2023-08-08 17:54 ` Stefan Kangas
2023-08-08 18:28 ` Eli Zaretskii
2023-08-08 13:37 ` Visuwesh
2023-08-08 13:52 ` Robert Pluim
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=DFFD8575-17FF-4CFB-B333-66FA2AD42F9B@acm.org \
--to=mattiase@acm.org \
--cc=65030@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@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).