GNU bug report logs - #9729
24.0.50; can't editing buffers while in another buffer i'm openning files

Previous Next

Package: emacs;

Reported by: sinoohe.mkh <at> gmail.com

Date: Tue, 11 Oct 2011 16:10:02 UTC

Severity: normal

Tags: confirmed

Merged with 13655, 39687

Found in versions 23.2, 24.0.50, 26.3

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: sinoohe.mkh <at> gmail.com, 9729 <at> debbugs.gnu.org
Subject: bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files
Date: Sun, 18 Jul 2021 15:37:40 +0300
> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: sinoohe.mkh <at> gmail.com,  9729 <at> debbugs.gnu.org
> Date: Sun, 18 Jul 2021 14:02:51 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > AFAIR, the prompt follows to another GUI frame because that frame gets
> > the focus-in event.  If I'm right, then it should also work with
> > emacsclient frames on terminals that support focus-in events.
> 
> Let's see...  I create a daemon and two "-nw" emacsclients, and then:
> 
> (setq focus-in-hook '((lambda () (message "focus %s" (selected-frame)))))
> 
> Clicking in the two clients does not display the message, so I guess
> that these terminals do not support focus-in events?  (This is
> Debian/bullseye under Gnome Shell, with "Terminal" as the terminal,
> which should be a very common environment.)

xterm does.  I don't know about Terminal.

> > Failing that, how to tell Emacs to switch to another frame, and would
> > the way to do that easier than just typing C-g and switching to the
> > client frame "by hand"?
> 
> I don't know the former, but perhaps the main problem with doing it
> manually today is that you first have to find the emacsclient that has
> the minibuffer active to hit `C-g' in it.  Hitting `C-g' in any other
> terminal does nothing.
> 
> Perhaps that is something that could be fixed?  That is, in an
> emacsclient context, `C-g' should interrupt the minibuffer action, no
> matter what frame it's happening in?

How can this work if we don't read input from the frame where you type
C-g?

But I don't consider myself an expert on this stuff, so maybe there is
a way.




This bug report was last modified 3 years and 136 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.