From: "Mattias Engdegård" <mattiase@acm.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>,
62847@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
gusbrs.2016@gmail.com
Subject: bug#62847: 29.0.90; Propertized space in Org Agenda's mode-name
Date: Sun, 16 Apr 2023 14:02:39 +0200 [thread overview]
Message-ID: <191D1749-C594-498C-B498-2C1770BBF413@acm.org> (raw)
In-Reply-To: <87mt38t69l.fsf@localhost>
16 apr. 2023 kl. 13.29 skrev Ihor Radchenko <yantar92@posteo.net>:
> I am wondering if there is any relevant warning raised by the byte
> compiler when doing something like
> (let ((str " ")) (add-text-properties 0 1 '(foo bar) str))
No, but it wouldn't be very hard to add one, but it would miss a lot of code that has no idea whether it is working on a string literal or not.
Counter to my usual preference for static checks I'd prefer a dynamic warning in this case because it would be precise and the run-time cost would likely be acceptable.
That requires a 'literal' flag for string objects and there's no obvious space for one, but perhaps we can grab the LSB of the `intervals` pointer.
Even if such a check defaults to off, it could be enabled selectively to root out bugs like this one. I'll see what I can do.
next prev parent reply other threads:[~2023-04-16 12:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 23:04 bug#62847: 29.0.90; Propertized space in Org Agenda's mode-name Gustavo Barros
2023-04-15 9:38 ` Ihor Radchenko
2023-04-15 9:49 ` Eli Zaretskii
2023-04-15 10:02 ` Ihor Radchenko
2023-04-15 10:24 ` Eli Zaretskii
2023-04-15 10:40 ` Ihor Radchenko
2023-04-15 10:55 ` Eli Zaretskii
2023-04-15 11:28 ` Gustavo Barros
2023-04-15 11:44 ` Ihor Radchenko
2023-04-15 11:49 ` Gustavo Barros
2023-04-15 12:08 ` Ihor Radchenko
2023-04-15 13:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-16 11:23 ` Ihor Radchenko
2023-04-16 11:49 ` Gustavo Barros
2023-04-15 11:38 ` Eli Zaretskii
2023-04-15 11:44 ` Ihor Radchenko
2023-04-15 11:45 ` Eli Zaretskii
2023-04-15 13:15 ` Mattias Engdegård
2023-04-16 11:29 ` Ihor Radchenko
2023-04-16 12:02 ` Mattias Engdegård [this message]
2023-04-16 12:17 ` Ihor Radchenko
2023-04-16 12:58 ` Eli Zaretskii
2023-04-16 13:14 ` Ihor Radchenko
2023-04-16 14:43 ` Eli Zaretskii
2023-04-16 14:52 ` Ihor Radchenko
2023-04-16 15:17 ` Eli Zaretskii
2023-04-16 14:51 ` Mattias Engdegård
2023-04-16 14:53 ` Mattias Engdegård
2023-04-16 12:38 ` Daniel Mendler
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=191D1749-C594-498C-B498-2C1770BBF413@acm.org \
--to=mattiase@acm.org \
--cc=62847@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gusbrs.2016@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=yantar92@posteo.net \
/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).