unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 53618@debbugs.gnu.org
Subject: bug#53618: 29.0.50; macroexp-warn-and-return incompatible change
Date: Fri, 11 Feb 2022 16:24:37 -0500	[thread overview]
Message-ID: <jwvtud514to.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <875yq2d2gb.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 29 Jan 2022 15:46:44 +0100")

I think both Alan and I have stated our diverging opinions.  I don't
think either of us is going to convince the other: we both have good
reasons which we mutually understand, we just disagree on the importance
to put on the various parts of the tradeoff.

So I'd appreciate a decision from the maintainers:

Should we keep the backward-incompatible code we currently have on
`master` or should we take my patch with its someone annoyingly
placed extra argument (or some yet distinct option)?


        Stefan






  parent reply	other threads:[~2022-02-11 21:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29  0:37 bug#53618: 29.0.50; macroexp-warn-and-return incompatible change Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-29 11:28 ` Alan Mackenzie
2022-01-29 14:46   ` Lars Ingebrigtsen
2022-01-29 15:02     ` Alan Mackenzie
2022-02-11 21:24     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-12  6:50       ` Lars Ingebrigtsen
2022-02-19 19:20         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=jwvtud514to.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53618@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).