From: Michael Albinus <michael.albinus@gmx.de>
To: Daniel Colascione <dancol@dancol.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: [PATCH] Really prevent quitting in sensitive contexts
Date: Tue, 14 Apr 2020 10:40:57 +0200 [thread overview]
Message-ID: <87zhbezch2.fsf@gmx.de> (raw)
In-Reply-To: <c55941c2-319f-af05-01f0-d5c20fdebf11@dancol.org> (Daniel Colascione's message of "Mon, 13 Apr 2020 23:56:14 -0700")
Daniel Colascione <dancol@dancol.org> writes:
Hi Daniel,
> No, it shouldn't. This use of with-local-quit can *never* be correct
> because a stray C-g can *always* interfere with a filter. Don't do
> long-running operations in process filters. Period. The fix isn't to
> make quitting these operations possible in some defined manner. The
> fix is not to do them in the first place.
How do you want to prevent use of such a basic operation like
`file-truename' in a process filter? And yes, in the remote case this
could be a "long-running operation".
Best regards, Michael.
next prev parent reply other threads:[~2020-04-14 8:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 2:05 [PATCH] Really prevent quitting in sensitive contexts Daniel Colascione
2020-03-12 2:20 ` Stefan Monnier
2020-03-12 2:32 ` Daniel Colascione
2020-03-12 10:07 ` Michael Albinus
2020-03-12 10:21 ` Robert Pluim
2020-03-12 10:33 ` Michael Albinus
2020-03-13 10:00 ` Michael Albinus
2020-04-14 6:56 ` Daniel Colascione
2020-04-14 8:40 ` Michael Albinus [this message]
2020-03-12 3:29 ` Óscar Fuentes
2020-03-12 7:21 ` Eli Zaretskii
2020-03-12 13:31 ` Richard Copley
2020-03-12 17:36 ` Drew Adams
2020-03-12 22:06 ` Stefan Monnier
2020-03-12 23:14 ` Richard Copley
2020-03-12 23:35 ` Stefan Monnier
2020-03-12 23:56 ` Richard Copley
2020-03-14 15:31 ` Drew Adams
2020-03-14 18:21 ` Stefan Monnier
2020-03-14 18:36 ` Drew Adams
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=87zhbezch2.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--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 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).