[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Non file buffers and default-directory
From: |
Michael Albinus |
Subject: |
Re: Non file buffers and default-directory |
Date: |
Wed, 26 Apr 2023 19:17:54 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Manuel Giraud <manuel@ledu-giraud.fr> writes:
Hi Manuel,
>> We could improve my proposal by adding a hook, which tells you which
>> buffers to remove. This hook could contain predicates for checking a
>> remote buffer-file-name, a remote process, or a romete dired buffer. And
>> this might be a new command in parallel to
>> tramp-cleanup-all-{buffers,connections}. Whether this is sufficient
>> we'll see, but this mechanism could be tuned after first experiences.
>
> Even if `tramp-cleanup-all-connections' is enough, I think that it is a
> good idea. It would keep closing a "remote" non [file|process|dired]
> from happening.
I've pushed the new command tramp-cleanup-some-buffers. As said, it
kills [file|process|dired] buffers. There is also the option
tramp-cleanup-some-buffers-hook, which allows you to configure this.
Best regards, Michael.
- Re: Non file buffers and default-directory, (continued)
- Re: Non file buffers and default-directory, Tomas Hlavaty, 2023/04/27
- Re: Non file buffers and default-directory, Tim Landscheidt, 2023/04/27
- Re: Non file buffers and default-directory, Manuel Giraud, 2023/04/27
- Re: Non file buffers and default-directory, Tomas Hlavaty, 2023/04/27
- Re: Non file buffers and default-directory, Manuel Giraud, 2023/04/23
- Re: Non file buffers and default-directory, Eli Zaretskii, 2023/04/23
- Re: Non file buffers and default-directory, Michael Albinus, 2023/04/22
- Re: Non file buffers and default-directory, Manuel Giraud, 2023/04/21
- Re: Non file buffers and default-directory,
Michael Albinus <=
- Re: Non file buffers and default-directory, Manuel Giraud, 2023/04/27
Re: Non file buffers and default-directory, Emanuel Berg, 2023/04/19
Re: Non file buffers and default-directory, Emanuel Berg, 2023/04/19