From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@linkov.net>
Cc: Giap Tran <txgvnn@gmail.com>, 49980@debbugs.gnu.org
Subject: bug#49980: 28.0.50; [PATCH] Should we have project-save-buffers?
Date: Fri, 13 Aug 2021 05:06:17 +0300 [thread overview]
Message-ID: <3ea58870-6b9a-41b9-c06e-d045ff9764b9@yandex.ru> (raw)
In-Reply-To: <87y297azuu.fsf@mail.linkov.net>
On 12.08.2021 10:55, Juri Linkov wrote:
>>> It would be nice to have a keybinding for this useful command,
>>> as there is 'C-x s', but 'C-x p s' is bound to 'project-shell'.
>>> Maybe then to bind it to 'C-x p S'?
>>
>> If we do end up adding this command, we could move project-shell to 'C-x
>> p E', for example, so that we don't spread shell-related commands over
>> different letters.
>
> Or to a new prefix map, e.g. 'C-x p x s' with mnemonics "eXecute Shell".
That would also displace project-execute-extended-command, which seems
gratuitous. And if we were putting different commands together to save
keymap space, 'project-compile' seems closer in purpose to
'project-shell' than 'project-execute-extended-command'.
Anyway, 'e' as a mnemonic for 'Eshell' or 'shEll' seems good enough for me.
>> But see my question in the other email.
>> Is there any reason not to just use 'save-some-buffers' (C-x s)?
>
> In bug#46374 we are adding a new option 'project-root'
> to 'save-some-buffers-default-predicate' that will allow
> 'C-x s' to save only files under the same project root.
That also seems to indicate that we don't need a separate command.
next prev parent reply other threads:[~2021-08-13 2:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 9:23 bug#49980: 28.0.50; [PATCH] Should we have project-save-buffers? Giap Tran
2021-08-11 6:52 ` Juri Linkov
2021-08-11 7:38 ` Giap Tran
2021-08-11 12:23 ` Dmitry Gutov
2021-08-12 7:55 ` Juri Linkov
2021-08-13 2:06 ` Dmitry Gutov [this message]
2021-08-13 7:12 ` Juri Linkov
2021-08-13 9:39 ` Arthur Miller
2021-08-13 16:05 ` Juri Linkov
2021-08-13 17:22 ` Arthur Miller
2021-08-14 2:25 ` Arthur Miller
2021-08-15 8:32 ` Juri Linkov
2021-08-15 10:44 ` Arthur Miller
2021-08-13 23:54 ` Dmitry Gutov
2021-08-14 2:46 ` Arthur Miller
2021-08-16 0:37 ` Dmitry Gutov
2021-08-16 1:19 ` Arthur Miller
2021-08-16 3:06 ` Dmitry Gutov
2021-08-16 13:22 ` Arthur Miller
2021-08-11 12:22 ` Dmitry Gutov
2021-08-11 13:40 ` Giap Tran
2021-08-13 2:11 ` Dmitry Gutov
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=3ea58870-6b9a-41b9-c06e-d045ff9764b9@yandex.ru \
--to=dgutov@yandex.ru \
--cc=49980@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=txgvnn@gmail.com \
/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).