From: Daimrod <daimrod@gmail.com>
To: 17361@debbugs.gnu.org
Subject: bug#17361: Tramp does not save history across sessions.
Date: Tue, 29 Apr 2014 17:34:41 +0900 [thread overview]
Message-ID: <87ppk0fs9q.fsf@tanger.home> (raw)
In-Reply-To: <87y4yopnuq.fsf@gmx.de> (Michael Albinus's message of "Tue, 29 Apr 2014 09:59:57 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> Daimrod <daimrod@gmail.com> writes:
>
>>> Wouldn't it be more consistent to modify `set-process-filter' and
>>> ´set-process-sentinel' to take care, when several filters or sentinels
>>> are added to a given process? Both functions could be equipped with an
>>> optional argument WHERE, which has the similar meaning as in
>>> `add-function'. Maybe just :before, :after and :replace shall be
>>> allowed, and one of them (:after?) could be the default.
>>
>> What about having a default sentinel/filter for all process that does
>> nothing (just a placeholder)?
>
> There are already `internal-default-process-filter' and
> `internal-default-process-sentinel'. They must be replaced, of course,
> when a new filter/sentinel is added.
Oh, I wasn't aware of those functions.
>> Then instead of using `set-process-filter' one could use
>> (add-function :whatever (process-filter process) ...)
>
> Nope. One would need to change all places those functions are called. I
> believe it is simpler to modify `set-process-filter' and
> `set-process-sentinel'.
I see. Thanks for the explanation.
--
Daimrod/Greg
next prev parent reply other threads:[~2014-04-29 8:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 13:16 bug#17361: Tramp does not save history across sessions Le Wang
2014-04-28 13:45 ` Michael Albinus
2014-04-28 15:09 ` Stefan Monnier
2014-04-28 18:01 ` Michael Albinus
2014-04-29 4:19 ` Stefan Monnier
2014-04-29 7:32 ` Michael Albinus
2014-04-29 7:39 ` Daimrod
2014-04-29 7:59 ` Michael Albinus
2014-04-29 8:34 ` Daimrod [this message]
2014-04-29 13:38 ` Stefan Monnier
2014-04-29 13:42 ` Stefan Monnier
2014-04-29 13:52 ` Michael Albinus
2014-04-29 14:30 ` Stefan Monnier
2014-04-29 14:42 ` Michael Albinus
2014-04-29 15:33 ` Stefan Monnier
2014-04-29 18:09 ` Michael Albinus
2014-04-29 19:40 ` Stefan Monnier
2014-04-29 21:24 ` Michael Albinus
2014-04-29 22:08 ` Stefan Monnier
2014-05-29 16:21 ` Glenn Morris
2014-04-28 15:26 ` Eli Zaretskii
2014-04-28 18:05 ` Michael Albinus
2014-04-28 18:15 ` Eli Zaretskii
2014-04-28 20:20 ` Stefan Monnier
2021-10-10 23:01 ` Stefan Kangas
2021-10-11 15:41 ` Michael Albinus
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=87ppk0fs9q.fsf@tanger.home \
--to=daimrod@gmail.com \
--cc=17361@debbugs.gnu.org \
/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).