GNU bug report logs -
#60930
30.0.50; 24.3 Choosing File Modes section of Emacs manual does not explain dealing with backup files
Previous Next
Reported by: Ihor Radchenko <yantar92 <at> posteo.net>
Date: Wed, 18 Jan 2023 10:58:01 UTC
Severity: normal
Found in version 30.0.50
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 60930 in the body.
You can then email your comments to 60930 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#60930
; Package
emacs
.
(Wed, 18 Jan 2023 10:58:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Ihor Radchenko <yantar92 <at> posteo.net>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Wed, 18 Jan 2023 10:58:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi,
The 24.3 Choosing File Modes section of Emacs manual explains how the
`auto-mode-alist' works, but fail to address an important point about
backup files being open in the major mode used for files with a name
stripped from the backup suffix:
Fifth—if Emacs still hasn’t found a suitable major mode—it looks at
the file’s name. The correspondence between file names and major modes
is controlled by the variable ‘auto-mode-alist’. Its value is a list in
which each element has this form,
<formal programmatic description of `auto-mode-alist' follows...>
I think that it is worth mentioning the backup file handling entry in
`auto-mode-alist' in the manual itself:
-----------
By default, `auto-mode-alist' contains:
("\\.~?[0-9]+\\.[0-9][-.0-9]*~?\\'" nil t)
("\\.\\(?:orig\\|in\\|[bB][aA][kK]\\)\\'" nil t)
meaning that backup files (for example, foo.txt~, foo.txt~12,
foo.txt.orig, foo.txt.in, foo.txt.bak) will use major mode as for
foo.txt - the file with backup suffix stripped.
-----
WDYT?
In GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, cairo version
1.17.6) of 2023-01-16 built on localhost
Repository revision: bb679244152dddd9949ca065aa6617457f7a7144
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101006
System Description: Gentoo Linux
--
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>
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Wed, 18 Jan 2023 14:07:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Ihor Radchenko <yantar92 <at> posteo.net>
:
bug acknowledged by developer.
(Wed, 18 Jan 2023 14:07:02 GMT)
Full text and
rfc822 format available.
Message #10 received at 60930-done <at> debbugs.gnu.org (full text, mbox):
> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Date: Wed, 18 Jan 2023 10:58:20 +0000
>
> Hi,
>
> The 24.3 Choosing File Modes section of Emacs manual explains how the
> `auto-mode-alist' works, but fail to address an important point about
> backup files being open in the major mode used for files with a name
> stripped from the backup suffix:
>
> Fifth—if Emacs still hasn’t found a suitable major mode—it looks at
> the file’s name. The correspondence between file names and major modes
> is controlled by the variable ‘auto-mode-alist’. Its value is a list in
> which each element has this form,
>
> <formal programmatic description of `auto-mode-alist' follows...>
>
> I think that it is worth mentioning the backup file handling entry in
> `auto-mode-alist' in the manual itself:
>
> -----------
> By default, `auto-mode-alist' contains:
>
> ("\\.~?[0-9]+\\.[0-9][-.0-9]*~?\\'" nil t)
> ("\\.\\(?:orig\\|in\\|[bB][aA][kK]\\)\\'" nil t)
>
> meaning that backup files (for example, foo.txt~, foo.txt~12,
> foo.txt.orig, foo.txt.in, foo.txt.bak) will use major mode as for
> foo.txt - the file with backup suffix stripped.
> -----
>
> WDYT?
The feature of "recursive extension stripping" was already documented
there. I added a few words about two examples of its usage (backup
files aren't the only one, and I see no reason to treat them specially
in this regard, let alone have the actual regexp in the manual).
However, I sincerely doubt that having this described in that place
will be discoverable enough. I also am not sure why you thought it
was so important to mention: it's an obscure implementation detail
intended to make Emacs DTRT, and as long it does TRT, why should users
worry?
But anyway, this is now in the manual for those who read the fine
print.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#60930
; Package
emacs
.
(Thu, 19 Jan 2023 11:36:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 60930-done <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
> The feature of "recursive extension stripping" was already documented
> there. I added a few words about two examples of its usage (backup
> files aren't the only one, and I see no reason to treat them specially
> in this regard, let alone have the actual regexp in the manual).
> However, I sincerely doubt that having this described in that place
> will be discoverable enough. I also am not sure why you thought it
> was so important to mention: it's an obscure implementation detail
> intended to make Emacs DTRT, and as long it does TRT, why should users
> worry?
I thought that it is important to mention because we got a bug report
claiming that opening backups of Org files in org-mode is not expected:
https://list.orgmode.org/25543.50706.554658.6937 <at> gargle.gargle.HOWL/
As for discoverability, an index entry might do.
--
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>
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#60930
; Package
emacs
.
(Thu, 19 Jan 2023 13:29:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 60930 <at> debbugs.gnu.org (full text, mbox):
> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: 60930-done <at> debbugs.gnu.org
> Date: Thu, 19 Jan 2023 11:36:09 +0000
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> > The feature of "recursive extension stripping" was already documented
> > there. I added a few words about two examples of its usage (backup
> > files aren't the only one, and I see no reason to treat them specially
> > in this regard, let alone have the actual regexp in the manual).
> > However, I sincerely doubt that having this described in that place
> > will be discoverable enough. I also am not sure why you thought it
> > was so important to mention: it's an obscure implementation detail
> > intended to make Emacs DTRT, and as long it does TRT, why should users
> > worry?
>
> I thought that it is important to mention because we got a bug report
> claiming that opening backups of Org files in org-mode is not expected:
> https://list.orgmode.org/25543.50706.554658.6937 <at> gargle.gargle.HOWL/
It isn't clear from that complaint what mistakes could happen.
Anyway, all that was requested there was to mention this in the
manual, so that others won't be surprised (if they read the manual).
> As for discoverability, an index entry might do.
Please suggest a useful index entry.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#60930
; Package
emacs
.
(Thu, 19 Jan 2023 13:35:01 GMT)
Full text and
rfc822 format available.
Message #19 received at 60930 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
> Anyway, all that was requested there was to mention this in the
> manual, so that others won't be surprised (if they read the manual).
Sure.
>> As for discoverability, an index entry might do.
>
> Please suggest a useful index entry.
choosing a major mode, in backup files
choosing a major mode, in encrypted files
--
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>
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#60930
; Package
emacs
.
(Thu, 19 Jan 2023 14:19:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 60930 <at> debbugs.gnu.org (full text, mbox):
> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: 60930 <at> debbugs.gnu.org
> Date: Thu, 19 Jan 2023 13:35:08 +0000
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> >> As for discoverability, an index entry might do.
> >
> > Please suggest a useful index entry.
>
> choosing a major mode, in backup files
> choosing a major mode, in encrypted files
Thanks, I added
@cindex backup files, choosing a major mode
@cindex encrypted files, choosing a major mode
because it is not useful to add several index entries that begin with
the same text and point to the same place. If you think how index
entries are used, you will understand why.
P.S. I'm not sure index entries will help discoverability (you need
to know what you are looking for to type an index entry), but adding
indexing can never do any harm.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#60930
; Package
emacs
.
(Fri, 20 Jan 2023 13:30:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 60930 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
> P.S. I'm not sure index entries will help discoverability (you need
> to know what you are looking for to type an index entry), but adding
> indexing can never do any harm.
I just need keywords. Most often, I invoke helm-info and search by index
(`Info-index-nodes'). Word ordering in the index does not matter for me
because of how helm matches candidates.
--
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>
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#60930
; Package
emacs
.
(Fri, 20 Jan 2023 13:51:02 GMT)
Full text and
rfc822 format available.
Message #28 received at 60930 <at> debbugs.gnu.org (full text, mbox):
> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: 60930 <at> debbugs.gnu.org
> Date: Fri, 20 Jan 2023 13:29:20 +0000
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> > P.S. I'm not sure index entries will help discoverability (you need
> > to know what you are looking for to type an index entry), but adding
> > indexing can never do any harm.
>
> I just need keywords. Most often, I invoke helm-info and search by index
> (`Info-index-nodes'). Word ordering in the index does not matter for me
> because of how helm matches candidates.
We cannot possibly write index entries on the assumption that they
will only be used through helm. The main client of index entries is
info.el.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#60930
; Package
emacs
.
(Sat, 21 Jan 2023 09:39:02 GMT)
Full text and
rfc822 format available.
Message #31 received at 60930 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
>> I just need keywords. Most often, I invoke helm-info and search by index
>> (`Info-index-nodes'). Word ordering in the index does not matter for me
>> because of how helm matches candidates.
>
> We cannot possibly write index entries on the assumption that they
> will only be used through helm. The main client of index entries is
> info.el.
Sure. But wouldn't it be nice to have an ability to do orederless-style
search across index keywords right from info.el?
--
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>
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#60930
; Package
emacs
.
(Sat, 21 Jan 2023 09:56:02 GMT)
Full text and
rfc822 format available.
Message #34 received at 60930 <at> debbugs.gnu.org (full text, mbox):
> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: 60930 <at> debbugs.gnu.org
> Date: Sat, 21 Jan 2023 09:39:14 +0000
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> >> I just need keywords. Most often, I invoke helm-info and search by index
> >> (`Info-index-nodes'). Word ordering in the index does not matter for me
> >> because of how helm matches candidates.
> >
> > We cannot possibly write index entries on the assumption that they
> > will only be used through helm. The main client of index entries is
> > info.el.
>
> Sure. But wouldn't it be nice to have an ability to do orederless-style
> search across index keywords right from info.el?
I don't think I understand what you mean by "orederless-style search"
in this context. Please elaborate.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#60930
; Package
emacs
.
(Sat, 21 Jan 2023 10:09:03 GMT)
Full text and
rfc822 format available.
Message #37 received at 60930 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
>> Sure. But wouldn't it be nice to have an ability to do orederless-style
>> search across index keywords right from info.el?
>
> I don't think I understand what you mean by "orederless-style search"
> in this context. Please elaborate.
getting matches for arbitrary keyword order in the completion buffer:
@cindex backup files, choosing a major mode
could be matched by typing, say, "file<SPC>major<SPC>back"
--
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>
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#60930
; Package
emacs
.
(Sat, 21 Jan 2023 11:37:01 GMT)
Full text and
rfc822 format available.
Message #40 received at 60930 <at> debbugs.gnu.org (full text, mbox):
> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: 60930 <at> debbugs.gnu.org
> Date: Sat, 21 Jan 2023 10:08:31 +0000
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> >> Sure. But wouldn't it be nice to have an ability to do orederless-style
> >> search across index keywords right from info.el?
> >
> > I don't think I understand what you mean by "orederless-style search"
> > in this context. Please elaborate.
>
> getting matches for arbitrary keyword order in the completion buffer:
>
> @cindex backup files, choosing a major mode
>
> could be matched by typing, say, "file<SPC>major<SPC>back"
That's up to the completion style you are using, right?
In any case, "i backup file RET" says there are just 8 candidates, so
it isn't a problem going over them one by one.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#60930
; Package
emacs
.
(Sat, 21 Jan 2023 13:35:02 GMT)
Full text and
rfc822 format available.
Message #43 received at 60930 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
>> could be matched by typing, say, "file<SPC>major<SPC>back"
>
> That's up to the completion style you are using, right?
>
> In any case, "i backup file RET" says there are just 8 candidates, so
> it isn't a problem going over them one by one.
Hmm. You are right. I rarely use "i" command because it works only
inside a single info manual. But otherwise "i" should indeed be
sufficient to search keywords efficiently.
--
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>
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 19 Feb 2023 12:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 59 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.