From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Le Wang <l26wang@gmail.com>, 17361@debbugs.gnu.org
Subject: bug#17361: Tramp does not save history across sessions.
Date: Tue, 29 Apr 2014 18:08:21 -0400 [thread overview]
Message-ID: <jwva9b3re8j.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <871twf96ch.fsf@gmx.de> (Michael Albinus's message of "Tue, 29 Apr 2014 23:24:46 +0200")
>> The only default that's backward compatible would be :override, which
>> basically defeats the purpose.
> In practice, your proposal means to throw away `set-process-sentinel'
> (and `set-process-filter').
[ Of course, only on the surface, since these are the low-level accessors
used by add-function. ]
> Since the default functions are already enabled, in most cases one
> shall use `add-function' instead.
There is a real problem with the default filter/sentinel, indeed.
Basically, add-function is a mechanism that allows combining functions
onto a "single function spot", so it provides the tool we need.
But another problem remains: for historical reasons (and for
convenience), the default filters/sentinels don't "do nothing". So in
many cases packages want to *replace* the default rather than extend it.
`set-process-filter' works well for those, until another package comes
along which needs to interact with it. Saying "use add-function"
doesn't really solve this problem, because we'll just replace
(set-process-filter PROC FUN)
with
(add-function :override (process-filter PROC) FUN)
which, just like set-process-filter, will override not just the default
filter but other filters added via add-function as well.
I haven't thought about how to really solve this problem. I'm open
to suggestions.
> (I don't oppose completely, I just want that we understand and agree
> such a change.)
I don't have a good answer yet, sorry.
Stefan
next prev parent reply other threads:[~2014-04-29 22:08 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
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 [this message]
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=jwva9b3re8j.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=17361@debbugs.gnu.org \
--cc=l26wang@gmail.com \
--cc=michael.albinus@gmx.de \
/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).