From: Eli Zaretskii <eliz@gnu.org>
To: Markus Triska <triska@metalevel.at>
Cc: 70326@debbugs.gnu.org
Subject: bug#70326: 30.0.50; Backup Files documentation does not match observed behaviour
Date: Thu, 11 Apr 2024 10:38:49 +0300 [thread overview]
Message-ID: <86zfu0tkl2.fsf@gnu.org> (raw)
In-Reply-To: <87frvsfmxn.fsf@metalevel.at> (message from Markus Triska on Thu, 11 Apr 2024 08:11:48 +0200)
> From: Markus Triska <triska@metalevel.at>
> Cc: 70326@debbugs.gnu.org
> Date: Thu, 11 Apr 2024 08:11:48 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > When have you last looked at the documentation in that part of the
> > manual?
>
> I last looked at it a few seconds ago to verify that it still reads as I
> originally posted it, and indeed it still reads:
>
> Emacs makes a backup for a file only the first time the file is
> saved from a buffer.
Here, it says this instead:
A “backup file” is a copy of the old contents of a file you are editing.
Emacs makes a backup file the first time you save a buffer into its
visited file.
> To repeat the original issue, this is not the behaviour I observe: There
> are cases where the file is saved from a buffer, and Emacs does not make
> a backup. I previously posted an example in this thread, and I hope you
> find it useful. Thank you a lot!
In the two cases you posted, the buffer was not saved into the file
visited by the buffer, so this is not "backup" in Emacs terms.
prev parent reply other threads:[~2024-04-11 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 18:24 bug#70326: 30.0.50; Backup Files documentation does not match observed behaviour Markus Triska
2024-04-10 18:28 ` Eli Zaretskii
2024-04-10 18:53 ` Markus Triska
2024-04-10 19:28 ` Eli Zaretskii
2024-04-10 19:46 ` Markus Triska
2024-04-11 4:00 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-11 5:59 ` Eli Zaretskii
2024-04-11 6:11 ` Markus Triska
2024-04-11 7: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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zfu0tkl2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70326@debbugs.gnu.org \
--cc=triska@metalevel.at \
/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.