[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#37176: 27.0.50; recursive-edit interrupted by invokation of emacscli
From: |
Stefan Monnier |
Subject: |
bug#37176: 27.0.50; recursive-edit interrupted by invokation of emacsclient |
Date: |
Sun, 25 Aug 2019 14:08:01 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
> Stefan, this is the result of your code from 13 years ago in
> server.el:
>
> (when (> (recursion-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.
> ;; Similarly with recursive-edits such as the splash screen.
> (run-with-timer 0 nil (lambda () (server-execute-continuation proc)))
> (top-level)))
>
> I could understand the rationale with the minibuffer, but I don't
> think I understand why the recursive-edit scenario needs the same
> treatment. Can you explain?
I can't remember wanting to do it for recursive-edit, so I'm pretty sure
the use of recursion-depth is just careless here and using
minibuffer-depth should work just as well.
Stefan