all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>, Spencer Baugh <sbaugh@janestreet.com>
Cc: 72019@debbugs.gnu.org
Subject: bug#72019: [PATCH] Add project argument to project-kill-buffers
Date: Thu, 11 Jul 2024 03:11:46 +0300	[thread overview]
Message-ID: <0ce21379-70a7-4859-9f3f-2f88d23dccbc@gutov.dev> (raw)
In-Reply-To: <8634ohnwpz.fsf@gnu.org>

On 10/07/2024 17:32, Eli Zaretskii wrote:
> In my book, prompting the user with the like of
> 
>    Project FOO disappeared, continue killing its buffers?

Without a change like the proposed, we don't have access to any FOO (the 
hook simply will return nil), so that's not something the general code 
can do.





  parent reply	other threads:[~2024-07-11  0:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 18:31 bug#72019: [PATCH] Add project argument to project-kill-buffers Spencer Baugh
2024-07-09 19:59 ` Dmitry Gutov
2024-07-10 11:43   ` Eli Zaretskii
2024-07-10 11:19 ` Eli Zaretskii
2024-07-10 13:27   ` Spencer Baugh
2024-07-10 14:32     ` Eli Zaretskii
2024-07-10 15:47       ` Spencer Baugh
2024-07-10 17:32         ` Eli Zaretskii
2024-07-10 17:42           ` Spencer Baugh
2024-07-10 17:54             ` Eli Zaretskii
2024-07-10 18:30               ` Spencer Baugh
2024-07-10 19:00                 ` Eli Zaretskii
2024-07-11  0:18                   ` Dmitry Gutov
2024-07-11  4:52                     ` Eli Zaretskii
2024-07-11 19:47                       ` Dmitry Gutov
2024-07-12  5:48                         ` Eli Zaretskii
2024-07-16  2:00                           ` Dmitry Gutov
2024-07-11  0:11       ` Dmitry Gutov [this message]
2024-07-11  4:50         ` Eli Zaretskii
2024-07-11 19:44           ` Dmitry Gutov
2024-07-12  5:47             ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0ce21379-70a7-4859-9f3f-2f88d23dccbc@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=72019@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=sbaugh@janestreet.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.