Subject: Re: bug#17361: Tramp does not save history across sessions.

From: Michael Albinus <[email-masked]>
Date: Mon, 28 Apr 2014 20:05:17 +0200

Eli Zaretskii <[email-masked]> writes:

>> So we need to support several sentinels per process.
>
> Or a protocol: if you install a sentinel, and another one already
> exists, call it after yours.

Yes. But all of the sentinels (or filters) must play the same game
then. When Tramp's sentinel is the first one being activated, it
shouldn't be thrown away by a `set-process-sentinel' call from another
library. We don't know in advance, in which order sentinels are
installed for a given process.

Best regards, Michael.