From: Noam Postavsky <npostavs@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 13400@debbugs.gnu.org, hendrik@askra.de
Subject: bug#13400: 23.4; overlapping process filter calls
Date: Wed, 07 Aug 2019 23:37:29 -0400 [thread overview]
Message-ID: <871rxws4xy.fsf@gmail.com> (raw)
In-Reply-To: <jwvv9vbii0c.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 05 Aug 2019 14:31:39 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> I'm pretty sure that while there might be use-cases for recursive
> invocation of filters, this is a very exceptional situation and the
> average programmer will not expect it and would be stumped if/when
> it happens.
>
> So the default should be to prevent it, with maybe some way to override
> it to cater to the exceptional case where recursive invocation
> is to be allowed.
>
> I think we could do that by setting a property on process object during
> filter invocation to postpone further filter invocations, and then the
> process filter could locally unset this property if it wants to allow
> recursive invocations.
Yeah, I suppose that would probably be better. Although then we have
some potential weird edge cases like what happens when when changing the
property during a recursive invocation.
next prev parent reply other threads:[~2019-08-08 3:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 10:11 bug#13400: 23.4; overlapping process filter calls Hendrik Tews
2019-07-27 3:38 ` Noam Postavsky
2019-07-27 8:24 ` Eli Zaretskii
2019-08-04 0:02 ` Noam Postavsky
2019-08-04 16:29 ` Eli Zaretskii
2019-08-05 18:31 ` Stefan Monnier
2019-08-08 3:37 ` Noam Postavsky [this message]
2019-08-08 13:36 ` Eli Zaretskii
2019-08-09 21:36 ` Stefan Monnier
2019-08-10 1:39 ` Noam Postavsky
2019-08-10 9:03 ` Stefan Monnier
2019-08-05 22:37 ` Hendrik Tews
2019-08-06 7:40 ` Stefan Monnier
2019-08-08 1:15 ` Noam Postavsky
2019-08-20 12:19 ` Noam Postavsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rxws4xy.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=13400@debbugs.gnu.org \
--cc=hendrik@askra.de \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.