From: Eli Zaretskii <eliz@gnu.org>
To: Reto Zimmermann <reto@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: justafrogg@gmail.com, 65464@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#65464: Emacs 29.1 - VHDL mode missing updates…
Date: Thu, 31 Aug 2023 16:00:23 +0300 [thread overview]
Message-ID: <831qfje594.fsf@gnu.org> (raw)
In-Reply-To: <0fdcbc09-19ec-fd2a-2064-2016bf5f0a6b@gnu.org> (message from Reto Zimmermann on Thu, 31 Aug 2023 13:32:12 +0200)
> Date: Thu, 31 Aug 2023 13:32:12 +0200
> Cc: stefankangas@gmail.com, justafrogg@gmail.com, 65464@debbugs.gnu.org
> From: Reto Zimmermann <reto@gnu.org>
>
> > Maybe we should discuss those changes you don't approve, and see
> > whether we indeed must have them in Emacs, or maybe find a different
> > way of solving whatever problems they intended to solve, way that you
> > would agree with.
> >
> > In general, if you keep developing and maintaining the package, I
> > think we should try very hard not to diverge what we have in Emacs.
>
> Agree. I will be busy the next few weeks, but after that I will look
> into it and start a discussion to resolve the differences.
Thanks.
> In the meantime I have a question: when byte-compiling vhdl-mode.el with
> Emacs 29.1 a 'defvar-1' ends up in vhdl-mode.elc, which causes an error
> in older Emacs versions:
>
> File mode specification error: (void-function defvar-1)
>
> Someone reported the error for Emacs 28.2, but I can't reproduce. I can
> reproduce on Emacs 15.1. Is this a known problem?
Stefan Monnier added that in commit 80ba4c17075, which was about
bug#55156. Stefan, can you answer this question? Did we make our
bytecode in Emacs 29 backward-incompatible?
next prev parent reply other threads:[~2023-08-31 13:00 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 [this message]
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
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=831qfje594.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65464@debbugs.gnu.org \
--cc=justafrogg@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.