unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 60930@debbugs.gnu.org
Subject: bug#60930: 30.0.50; 24.3 Choosing File Modes section of Emacs manual does not explain dealing with backup files
Date: Thu, 19 Jan 2023 15:28:12 +0200	[thread overview]
Message-ID: <837cxipsb7.fsf@gnu.org> (raw)
In-Reply-To: <878rhy4uza.fsf@localhost> (message from Ihor Radchenko on Thu, 19 Jan 2023 11:36:09 +0000)

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: 60930-done@debbugs.gnu.org
> Date: Thu, 19 Jan 2023 11:36:09 +0000
> 
> Eli Zaretskii <eliz@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@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.





  reply	other threads:[~2023-01-19 13:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 10:58 bug#60930: 30.0.50; 24.3 Choosing File Modes section of Emacs manual does not explain dealing with backup files Ihor Radchenko
2023-01-18 14:06 ` Eli Zaretskii
2023-01-19 11:36   ` Ihor Radchenko
2023-01-19 13:28     ` Eli Zaretskii [this message]
2023-01-19 13:35       ` Ihor Radchenko
2023-01-19 14:17         ` Eli Zaretskii
2023-01-20 13:29           ` Ihor Radchenko
2023-01-20 13:50             ` Eli Zaretskii
2023-01-21  9:39               ` Ihor Radchenko
2023-01-21  9:55                 ` Eli Zaretskii
2023-01-21 10:08                   ` Ihor Radchenko
2023-01-21 11:36                     ` Eli Zaretskii
2023-01-21 13:34                       ` Ihor Radchenko

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=837cxipsb7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60930@debbugs.gnu.org \
    --cc=yantar92@posteo.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).