From: Philip Kaludercic <philipk@posteo.net>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "Simen Heggestøyl" <simenheg@runbox.com>, 49465@debbugs.gnu.org
Subject: bug#49465: Fwd: Re: bug#49465: 28.0.50; project-kill-buffers: include shell buffers?
Date: Sat, 10 Jul 2021 13:17:58 +0000 [thread overview]
Message-ID: <871r86wbnd.fsf@posteo.net> (raw)
In-Reply-To: <cb2ef548-5b5f-d834-9eab-2e441e229c0b@yandex.ru> (Dmitry Gutov's message of "Sat, 10 Jul 2021 13:26:22 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 10.07.2021 10:33, Philip Kaludercic wrote:
>> I think that adding the shells created by C-x p {e,s} would be good, but
>> I am not sure if we want to always kill a shell buffer, that might just
>> happen to be in a project directory.
>
> IDK, most of the time I create Eshell by calling the "plain" eshell
> command somewhere inside the project. And it still feels like
> belonging to that project. So I'd probably like for them to be cleaned
> out too.
>
> Do you envision a particular scenario where you wouldn't want this to
> happen?
A simple example would be if I start a shell session, later on cd into a
project, start working on it and then want to clean up the project. The
shell that might contain relevant information outside of the project I
just worked on would also be killed.
--
Philip Kaludercic
next prev parent reply other threads:[~2021-07-10 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4a4ce7e8-34c0-cc0a-118a-c9753ba68347@yandex.ru>
[not found] ` <87eec6wrlm.fsf@posteo.net>
2021-07-10 10:26 ` bug#49465: Fwd: Re: bug#49465: 28.0.50; project-kill-buffers: include shell buffers? Dmitry Gutov
2021-07-10 13:17 ` Philip Kaludercic [this message]
2021-07-17 23:46 ` Dmitry Gutov
2021-12-15 13:49 ` Simen Heggestøyl
2021-12-17 1:21 ` Dmitry Gutov
2021-12-17 7:56 ` Simen Heggestøyl
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=871r86wbnd.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=49465@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=simenheg@runbox.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).