unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 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: Tue, 29 Mar 2016 09:30:10 -0700 (PDT)	[thread overview]
Message-ID: <926e4dde-9802-450b-b61c-66fd3d56434a@default> (raw)
In-Reply-To: <m3wpolb8js.fsf@gnus.org>

> During an unrelated discussion on emacs-devel, it turns out that
> virtually everybody

Uh, 3 people?  OK, 3 out of the 3 who bothered to say something about
this.  But "virtually everybody" might be a bit of an exaggeration, no?

> is in the habit of making a change, then deleting
> the change, just to make `C-x C-s' work.
>
> This means that there is a need for Emacs to offer a command to save
> buffers, even if they aren't changed.

No, it does not mean that.

(But I have no objection to your adding such a command.)

> 1) Have the interactive `C-x C-s' command always save the buffer, no
> matter whether it's unchanged or not.  I think many people would object
> to this, as they're used to just `C-x C-s'-ing idly while thinking of
> other things.

I would object, for one.  If you feel you must add a command, add
a command.  But please do not mess with `C-x C-s'.

> 2) Have the prefix to that command save the unchanged buffer.  This
> would be the obvious choice, but:

<yes, a prefix arg already has meaning for `C-x C-s'>

> Eh.  Four `C-u's?  I don't think so.  We could bind `C-x C-s' to a new
> `save-buffer-command' that has different prefix rules.  Does anybody use
> the backup stuff?

Yes, of course they do.  Hard to believe you wonder about this,
or would even consider changing the UI of `C-x C-s'.

> 3) Add a new keystroke.
> 
> 4) Something else.

Just add the command.  Users can bind it themselves, if they like.
Time will then tell whether Emacs should at some point bind a key
for the command by default.

5) Use `C-u C-x C-w RET' instead of `C-x C-s'.  If you like, bind
that to another key.

Much ado about nothing, IMO.





  reply	other threads:[~2016-03-29 16:30 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 [this message]
     [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
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=926e4dde-9802-450b-b61c-66fd3d56434a@default \
    --to=drew.adams@oracle.com \
    --cc=23151@debbugs.gnu.org \
    --cc=larsi@gnus.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).