From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, 51094-close@debbugs.gnu.org
Subject: bug#51094: Check if run-with{-idle, }-timer needs to create a timer
Date: Fri, 08 Oct 2021 11:33:27 +0000 [thread overview]
Message-ID: <878rz37nug.fsf@posteo.net> (raw)
In-Reply-To: <87y273py3f.fsf_-_@gnus.org> (Lars Ingebrigtsen's message of "Fri, 08 Oct 2021 13:14:44 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Yes, the semantics of running things from a timer are different from
>> running them in the normal flow, so we can't transform 0-delay timers
>> into funcalls.
>
> See for instance:
>
> (when (> (minibuffer-depth) 0)
> ;; We're inside a minibuffer already, so if the emacs-client is trying
> ;; to open a frame on a new display, we might end up with an unusable
> ;; frame because input from that display will be blocked (until exiting
> ;; the minibuffer). Better exit this minibuffer right away.
> (run-with-timer 0 nil (lambda () (server-execute-continuation proc)))
>
> So this change is a no go.
Ok, that makes sense.
One last question, would it make sense to provide a function like
run-with-timer that would work like my patch?
--
Philip Kaludercic
next prev parent reply other threads:[~2021-10-08 11:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 9:36 bug#51094: Check if run-with{-idle,}-timer needs to create a timer Philip Kaludercic
2021-10-08 10:46 ` bug#51094: Check if run-with{-idle, }-timer " Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-08 10:53 ` Lars Ingebrigtsen
2021-10-08 11:14 ` Lars Ingebrigtsen
2021-10-08 11:33 ` Philip Kaludercic [this message]
2021-10-08 12:29 ` Lars Ingebrigtsen
2021-10-08 11:03 ` Philip Kaludercic
2021-10-08 11:29 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-08 11:13 ` Eli Zaretskii
2021-10-08 11:08 ` Eli Zaretskii
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=878rz37nug.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=51094-close@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.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).