From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Richard Stallman <rms@gnu.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 23151@debbugs.gnu.org
Subject: bug#23151: 25.1.50; Emacs should have a convenient command for saving unchanged buffers
Date: Wed, 30 Mar 2016 16:19:11 +0200 [thread overview]
Message-ID: <87fuv86obk.fsf@wanadoo.es> (raw)
In-Reply-To: <E1alEwS-0001GC-5q@fencepost.gnu.org> (Richard Stallman's message of "Wed, 30 Mar 2016 08:09:44 -0400")
Richard Stallman <rms@gnu.org> writes:
> > During an unrelated discussion on emacs-devel, it turns out that
> > virtually everybody is in the habit of making a change, then deleting
> > the change, just to make `C-x C-s' work.
>
> That's how I do it. It's convenient and natural.
If certain modes are enabled, that method does not give back the
original content depending on the exact keys used.
> > This means that there is a
> > need for Emacs to offer a command to save buffers, even if they aren't
> > changed.
>
> I draw a different conclusion: Emacs already has a simple and obvious
> way to save an unchanged buffer, so no new features are needed for this.
I'll like to see that feature implemented as a safe method of forcing
Emacs to save the file without altering the buffer's content.
next prev parent reply other threads:[~2016-03-30 14:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 15:36 bug#23151: 25.1.50; Emacs should have a convenient command for saving unchanged buffers Lars Magne Ingebrigtsen
2016-03-29 16:30 ` Drew Adams
[not found] ` <mailman.8597.1459265831.843.bug-gnu-emacs@gnu.org>
2016-03-29 19:14 ` Alan Mackenzie
2016-03-29 23:07 ` Johan Bockgård
2016-03-29 23:41 ` Drew Adams
2016-03-30 12:09 ` Richard Stallman
2016-03-30 14:19 ` Óscar Fuentes [this message]
2016-03-30 15:05 ` Andreas Schwab
2016-03-30 15:40 ` Óscar Fuentes
2016-03-30 16:04 ` Andreas Schwab
2016-03-30 16:28 ` Óscar Fuentes
2016-03-30 17:02 ` Drew Adams
2016-03-30 16:12 ` Drew Adams
2016-03-31 7:54 ` Richard Stallman
2016-03-31 16:11 ` John Wiegley
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=87fuv86obk.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=23151@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
/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).