Re: Non file buffers and default-directory

[Manuel Giraud]

Michael Albinus <michael.albinus@gmx.de> writes:

[...]

> Usually, tramp-cleanup-all-connections is sufficient.
> tramp-cleanup-all-buffers let the remote buffers disappear in order to
> not let you reconnect via a mistake, like openening a file in dired.

Ok.  I didn't know about that so maybe I could live with that using
`tramp-cleanup-all-connections' only.

> 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.  But Emanuel Berg said it does not see this behaviour
with `tramp-cleanup-all-buffers': am I the only one?

Recipe:
        - C-x d /-:remotehost:
        - M-x man man
        - M-x tramp-cleanup-all-buffers

Is the *Man man* buffer closed?
-- 
Manuel Giraud