From: Eli Zaretskii <eliz@gnu.org>
To: Hong Xu <hong@topbug.net>
Cc: 53199-done@debbugs.gnu.org
Subject: bug#53199: [PATCH] * Clarify that @var{auto-mode-alist} is searched
Date: Wed, 12 Jan 2022 14:38:46 +0200 [thread overview]
Message-ID: <834k696sdl.fsf@gnu.org> (raw)
In-Reply-To: <54b3ee39-9f6c-5827-807f-227ecd302e4f@topbug.net> (message from Hong Xu on Tue, 11 Jan 2022 16:46:22 -0800)
> From: Hong Xu <hong@topbug.net>
> Date: Tue, 11 Jan 2022 16:46:22 -0800
>
> doc/lispref/modes.texi | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/doc/lispref/modes.texi b/doc/lispref/modes.texi
> index 5fc831536e82..0bd1fc51febf 100644
> --- a/doc/lispref/modes.texi
> +++ b/doc/lispref/modes.texi
> @@ -750,9 +750,10 @@ Auto Major Mode
> When you visit a file whose expanded file name (@pxref{File Name
> Expansion}), with version numbers and backup suffixes removed using
> @code{file-name-sans-versions} (@pxref{File Name Components}), matches
> -a @var{regexp}, @code{set-auto-mode} calls the corresponding
> -@var{mode-function}. This feature enables Emacs to select the proper
> -major mode for most files.
> +a @var{regexp}, @code{set-auto-mode} calls the @var{mode-function}
> +that corresponds to the first such @var{regexp} in
> +@var{auto-mode-alist}. This feature enables Emacs to select the
> +proper major mode for most files.
Thanks. I decided to clarify this in a slightly different way, by
adding the following sentence after the description of the matching
process:
If @code{auto-mode-alist} has more than one element whose @var{regexp}
matches the file name, Emacs will use the first match.
With that, I'm closing the bug.
prev parent reply other threads:[~2022-01-12 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 0:46 bug#53199: [PATCH] * Clarify that @var{auto-mode-alist} is searched Hong Xu
[not found] ` <handler.53199.B.164194839726056.ack@debbugs.gnu.org>
2022-01-12 4:50 ` bug#53199: Acknowledgement ([PATCH] * Clarify that @var{auto-mode-alist} is searched) Hong Xu
2022-01-12 12:38 ` Eli Zaretskii [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=834k696sdl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53199-done@debbugs.gnu.org \
--cc=hong@topbug.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).