From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Gemini Lasswell <gazally@runbox.com>, 64536@debbugs.gnu.org
Subject: bug#64536: 30.0.50; Make cl-print put buttons on ellipses
Date: Mon, 14 Aug 2023 15:15:40 +0000 [thread overview]
Message-ID: <874jl1psdf.fsf@localhost> (raw)
In-Reply-To: <jwv5y5hpvrw.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> I am not sure if this can be done on byte compiler level.
>
> Not sure either. A compiler-macro placed on `make-text-button` and
> `make-button` could look for a `:type` arg and check its obsolescence,
> but I don't know how effective it would be.
Maybe not that bad.
Of course, it will miss :type values not known at compile time, but it
is the same issue even with ordinary obsolete variables/functions that
are used not by their literal name.
>> For runtime, after skimming through button.el, it looks like
>> `button-category-symbol' might be used to throw a warning when obsolete
>> button type is being used.
>
> Runtime check are easier and more reliable, indeed, but also more
> annoying and directed at the wrong person :-(
Makes sense. Although, they can be useful for maintainers if such checks
can be enabled explicitly, by flipping a variable.
We used such approach for org-element--cache-self-verify.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2023-08-14 15:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 4:42 bug#64536: 30.0.50; Make cl-print put buttons on ellipses Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-13 23:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-11 7:53 ` Ihor Radchenko
2023-08-12 5:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-12 8:39 ` Ihor Radchenko
2023-08-12 18:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-13 9:26 ` Ihor Radchenko
2023-08-13 16:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-14 11:01 ` Ihor Radchenko
2023-08-14 14:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-14 15:15 ` Ihor Radchenko [this message]
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=874jl1psdf.fsf@localhost \
--to=yantar92@posteo.net \
--cc=64536@debbugs.gnu.org \
--cc=gazally@runbox.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).