From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: reto@gnu.org, mattias.engdegard@gmail.com, 65464@debbugs.gnu.org,
stefankangas@gmail.com
Subject: bug#65464: Emacs 29.1 - VHDL mode missing updates…
Date: Tue, 12 Sep 2023 10:08:06 -0400 [thread overview]
Message-ID: <jwvv8cfeban.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83msxrpr0n.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 12 Sep 2023 14:31:04 +0300")
>> We just need to make use of that info.
> Make use how? In most cases the byte-code is compatible both backward
> and forward, so displaying a warning would be an annoyance that 99% of
> time is unjustified.
Actually, forward compatibility is often broken between major versions.
Stefan
prev parent reply other threads:[~2023-09-12 14:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 16:15 bug#65464: Emacs 29.1 - VHDL mode missing updates… Tracy’s Gmail
2023-08-23 10:47 ` Stefan Kangas
2023-08-29 13:23 ` Reto Zimmermann
2023-08-29 16:46 ` Stefan Kangas
2023-08-29 16:56 ` Tracy’s Gmail
2023-08-29 18:25 ` Stefan Kangas
2023-08-30 12:23 ` Reto Zimmermann
2023-08-30 13:38 ` Eli Zaretskii
2023-08-31 11:32 ` Reto Zimmermann
2023-08-31 13:00 ` Eli Zaretskii
2023-08-31 14:59 ` Stefan Kangas
2023-08-31 18:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 7:47 ` Eli Zaretskii
2023-09-11 2:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 11:40 ` Eli Zaretskii
2023-09-02 9:20 ` Mattias Engdegård
2023-09-11 16:21 ` Mattias Engdegård
2023-09-11 22:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 6:59 ` Mattias Engdegård
2023-09-12 11:31 ` Eli Zaretskii
2023-09-12 14:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvv8cfeban.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=65464@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=reto@gnu.org \
--cc=stefankangas@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.