From: Giap Tran <txgvnn@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 49980@debbugs.gnu.org
Subject: bug#49980: 28.0.50; [PATCH] Should we have project-save-buffers?
Date: Wed, 11 Aug 2021 20:40:19 +0700 [thread overview]
Message-ID: <87v94cumkc.fsf@gmail.com> (raw)
In-Reply-To: <feeff840-0943-5617-6927-484ef59ff11c@yandex.ru> (Dmitry Gutov's message of "Wed, 11 Aug 2021 15:22:35 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> Is there any reason not to just use 'save-some-buffers' (C-x s)?
>
> Do you often want to leave some buffers unsaved?
Oh, so funny, I used Emacs for over 4 years and I don't know this
function. Looks like I just need this to solve my problem
> Then project-save-buffers could be on 'C-x p s'.
Is `project-save-buffers necessary anymore? If anyone opens many projects
with unsaved buffers. Maybe they need that because they don't want to
save buffers not in this project. I think we don't need
keybinding for that. We can use M-x, up to you :D
--
Giap Tran <txgvnn@gmail.com>
GnuPG/0xE655BF766A56995D
next prev parent reply other threads:[~2021-08-11 13:40 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
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 [this message]
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=87v94cumkc.fsf@gmail.com \
--to=txgvnn@gmail.com \
--cc=49980@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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).