From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier via Mailing list for Emacs changes <emacs-devel@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: master 59f8c56d9e: files.el (major-mode-remap-alist): New custom var (bug#58075)
Date: Mon, 03 Oct 2022 18:43:43 +0200 [thread overview]
Message-ID: <87wn9g6eo0.fsf@gnus.org> (raw)
In-Reply-To: <20221003151804.CBDC8C0004A@vcs2.savannah.gnu.org> (Stefan Monnier via Mailing list for Emacs changes's message of "Mon, 3 Oct 2022 11:18:00 -0400 (EDT)")
Stefan Monnier via Mailing list for Emacs changes <emacs-diffs@gnu.org>
writes:
> * lisp/files.el (major-mode-remap-alist): New custom var.
> (set-auto-mode--last): New var.
> (set-auto-mode-0): Obey `major-mode-remap-alist`.
I'm seeing a number of test failures currently:
4 files contained unexpected results:
lisp/textmodes/tildify-tests.log
lisp/textmodes/reftex-tests.log
lisp/gnus/mml-sec-tests.log
lisp/electric-tests.log
I didn't think they had anything to do with this, but:
Test tildify-space-undo-test-tex backtrace:
nil()
tex--redirect-to-submode(#f(compiled-function () (interactive nil) #
apply(tex--redirect-to-submode #f(compiled-function () (interactive
tex-mode()
funcall(tex-mode)
in
3 unexpected results:
FAILED tildify-space-test-tex
FAILED tildify-space-undo-test-tex
FAILED tildify-test-tex
I haven't checked whether all these failures are related to this,
though.
(This is --with-native-compilation, if it makes a difference.)
next parent reply other threads:[~2022-10-03 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166481028045.20591.9765647363011981889@vcs2.savannah.gnu.org>
[not found] ` <20221003151804.CBDC8C0004A@vcs2.savannah.gnu.org>
2022-10-03 16:43 ` Lars Ingebrigtsen [this message]
2022-10-04 0:48 ` master 59f8c56d9e: files.el (major-mode-remap-alist): New custom var (bug#58075) Stefan Monnier
2022-10-04 1:01 ` Lars Ingebrigtsen
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=87wn9g6eo0.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--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).