unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Elken <me@elken.dev>, Juri Linkov <juri@linkov.net>
Cc: 65928@debbugs.gnu.org
Subject: bug#65928: [PATCH] Introduce 'project-save-buffers'
Date: Thu, 14 Sep 2023 17:30:59 +0300	[thread overview]
Message-ID: <ff45c9c9-5c6f-9c6b-10c0-fa10939a16db@gutov.dev> (raw)
In-Reply-To: <CAF52069-CA61-4CE2-B668-F3C0080BC9BA@elken.dev>

On 14/09/2023 16:45, Elken via Bug reports for GNU Emacs, the Swiss army 
knife of text editors wrote:
> Implemented somewhat yeah, but I think it's sensible and more 
> discoverable having one here as you say. :)

I suppose the main question is whether we want a 
project-save-some-buffers (one that can iterate through unsaved buffers 
but can also save them all with an extra keypress) or a straight copy of 
Projectile's command that just saves all buffers.

I don't use the iteration ability often, but once in a blue moon it does 
come in handy. Though perhaps one can continue using save-some-buffer 
for that (with the default predicate or not).





  parent reply	other threads:[~2023-09-14 14:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 21:26 bug#65928: [PATCH] Introduce 'project-save-buffers' me--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-14  6:51 ` Juri Linkov
2023-09-14 13:45   ` Elken via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-14 14:09     ` Stefan Kangas
2023-09-14 14:12       ` Dmitry Gutov
2023-09-14 14:18       ` me--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-14 14:30     ` Dmitry Gutov [this message]
2023-09-14 14:07   ` Stefan Kangas
2023-09-14 14:13     ` Dmitry Gutov
2023-09-14 14:16     ` me--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-15  6:32     ` Juri Linkov
2023-09-15 16:39       ` Dmitry Gutov
2023-09-18  6:56         ` Juri Linkov

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=ff45c9c9-5c6f-9c6b-10c0-fa10939a16db@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=65928@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=me@elken.dev \
    /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).