From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 70784@debbugs.gnu.org
Subject: bug#70784: Abolish string resizing
Date: Sun, 05 May 2024 14:09:10 -0400 [thread overview]
Message-ID: <jwva5l4qgnp.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <9416BCF1-C394-483A-80DC-D6BBD10F48FE@gmail.com> ("Mattias Engdegård"'s message of "Sun, 5 May 2024 16:18:16 +0200")
> That's fine, but a warning might help in emacs-30 to prepare for making
> resizing an error in emacs-31.
> Here's how that would work: the first 5 times (say), emit a warning like
>
> Warning: `aset' on a multibyte string with char value #x2022 will become an error in Emacs 31
>
> followed by a truncated stack trace, just enough to help the user (or
> someone helping out) see what package is responsible.
Similar to what I do in `track-changes.el` when we detect a missing
call to `after/before-change-functions`? I like that.
If the warning is too annoying, we could do like I did there, i.e. only
emit the warning when running in a non-release Emacs (i.e. when
`emacs-version` has 2 dots), and offer a variable to control whether to
emit the warning or not.
Stefan
next prev parent reply other threads:[~2024-05-05 18:09 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 12:33 bug#70784: Abolish string resizing Mattias Engdegård
2024-05-05 14:04 ` Eli Zaretskii
2024-05-05 14:18 ` Mattias Engdegård
2024-05-05 15:23 ` Eli Zaretskii
2024-05-05 16:55 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-05 17:10 ` Eli Zaretskii
2024-05-05 18:09 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-05 18:14 ` Eli Zaretskii
2024-05-05 20:08 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 1:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 6:02 ` Gerd Möllmann
2024-05-08 23:25 ` Richard Stallman
2024-05-08 23:24 ` Richard Stallman
2024-05-09 1:14 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 9:02 ` Stefan Kangas
2024-05-26 9:17 ` Eli Zaretskii
2024-05-26 18:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 18:45 ` Eli Zaretskii
2024-05-27 3:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-28 2:23 ` Richard Stallman
2024-05-05 18:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-05-05 20:24 ` Mattias Engdegård
2024-05-05 21:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-11 15:20 ` Mattias Engdegård
2024-05-11 16:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 17:30 ` Mattias Engdegård
2024-05-15 17:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 19:35 ` Mattias Engdegård
2024-05-25 11:24 ` Mattias Engdegård
2024-05-25 11:37 ` Eli Zaretskii
2024-05-25 13:01 ` Mattias Engdegård
2024-05-06 0:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 1:56 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 11:35 ` Eli Zaretskii
2024-05-06 12:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-07 11:13 ` Eli Zaretskii
2024-05-07 13:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 2:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 4:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 10:57 ` Eli Zaretskii
2024-05-06 11:26 ` Eli Zaretskii
2024-05-06 12:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-07 11:19 ` Eli Zaretskii
2024-05-08 23:25 ` Richard Stallman
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=jwva5l4qgnp.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=70784@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattias.engdegard@gmail.com \
--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).