bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files

bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files

[sinoohe.mkh]

Hi,
1)run emacs --daemon
2)open two emacsclient on two seprate terminals
3)on first emacs: C-x C-f   (and I don't Enter any file address)
4)go to second terminal running emacsclient 
5)I can't edit that buffer while go back to the first terminal (that I entered C-x C-f)
and enter C-g

I don't know if it's a feature or is it a bug?!!
But I think I should be able to edit the buffer while C-x C-f is running in another terminal


In GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.24.5)
 of 2011-09-26 on myhost
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US.UTF-8
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
ESC [ > 0 ; 1 1 5 ; 0 c ESC [ > 0 ; 1 1 5 ; 0 c C-x 
C-f C-g <switch-frame> s d d s d s C-p C-p C-p ESC 
x C-g <switch-frame> ESC x r e ESC x ESC x C-g ESC 
x r e g DEL p o TAB r TAB RET

Recent messages:
("emacs")
Starting Emacs daemon.
When done with this frame, type C-x 5 0 [2 times]
Quit [2 times]
completing-read-default: Command attempted to use minibuffer while in minibuffer [2 times]
Quit [2 times]
Making completion list...

Load-path shadows:
None found.

Features:
(shadow sort gnus-util mail-extr message format-spec rfc822 mml mml-sec
mm-decode mm-bodies mm-encode mail-parse rfc2231 rfc2047 rfc2045
ietf-drums mm-util mail-prsvr mailabbrev mail-utils gmm-utils mailheader
emacsbug help-mode easymenu view server time-date tooltip ediff-hook
vc-hooks lisp-float-type mwheel x-win x-dnd tool-bar dnd fontset image
fringe lisp-mode register page menu-bar rfn-eshadow timer select
scroll-bar mouse jit-lock font-lock syntax facemenu font-core frame cham
georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao
korean japanese hebrew greek romanian slovak czech european ethiopic
indian cyrillic chinese case-table epa-hook jka-cmpr-hook help simple
abbrev minibuffer loaddefs button faces cus-face files text-properties
overlay sha1 md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote make-network-process dbusbind
dynamic-setting system-font-setting font-render-setting move-toolbar gtk
x-toolkit x multi-tty emacs)

bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files

[Glenn Morris]

sinoohe.mkh@gmail.com wrote:

> 1)run emacs --daemon
> 2)open two emacsclient on two seprate terminals
> 3)on first emacs: C-x C-f   (and I don't Enter any file address)
> 4)go to second terminal running emacsclient 
> 5)I can't edit that buffer while go back to the first terminal (that I entered C-x C-f)
> and enter C-g

Does it help to

(setq enable-recursive-minibuffers t)

bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files

[mehran khajavi]

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]

no,
nothing new happened!
the problem still existing

On Tue, Oct 11, 2011 at 9:20 PM, Glenn Morris <rgm@gnu.org> wrote:
> sinoohe.mkh@gmail.com wrote:
>
>> 1)run emacs --daemon
>> 2)open two emacsclient on two seprate terminals
>> 3)on first emacs: C-x C-f   (and I don't Enter any file address)
>> 4)go to second terminal running emacsclient
>> 5)I can't edit that buffer while go back to the first terminal (that I
entered C-x C-f)
>> and enter C-g
>
> Does it help to
>
> (setq enable-recursive-minibuffers t)
>

[-- Attachment #2: Type: text/html, Size: 779 bytes --]

bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files

[Lars Ingebrigtsen]

sinoohe.mkh@gmail.com writes:

> 1)run emacs --daemon
> 2)open two emacsclient on two seprate terminals
> 3)on first emacs: C-x C-f   (and I don't Enter any file address)
> 4)go to second terminal running emacsclient 
> 5)I can't edit that buffer while go back to the first terminal (that I entered C-x C-f)
> and enter C-g

(I'm going through old bug reports that unfortunately got little response at
the time.)

I can confirm that this problem is still present in Emacs 28.  But I
vaguely recall there being some discussion about this recently -- has
Emacs gotten a way around this issue now?  Anybody remember?

(enable-recursive-minibuffers doesn't help.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 16 Jul 2021 16:36:24 +0200
> Cc: 9729@debbugs.gnu.org
> 
> > 1)run emacs --daemon
> > 2)open two emacsclient on two seprate terminals
> > 3)on first emacs: C-x C-f   (and I don't Enter any file address)
> > 4)go to second terminal running emacsclient 
> > 5)I can't edit that buffer while go back to the first terminal (that I entered C-x C-f)
> > and enter C-g
> 
> (I'm going through old bug reports that unfortunately got little response at
> the time.)
> 
> I can confirm that this problem is still present in Emacs 28.  But I
> vaguely recall there being some discussion about this recently -- has
> Emacs gotten a way around this issue now?  Anybody remember?

It's a basic limitation of our keyboard input: we can only read from a
single frame at a time.

bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

> It's a basic limitation of our keyboard input: we can only read from a
> single frame at a time.

I guess that'd be difficult to fix...  but could we do something about
how this works in an emacsclient context?

That is, if you `M-x' and then change frames in a normal GUI Emacs, the
`M-x' will follow you around.  There's no such concept in emacsclient as
an "active frame", but could we somehow make minibuffer commands abort
the action in other frames?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: sinoohe.mkh@gmail.com,  9729@debbugs.gnu.org
> Date: Sat, 17 Jul 2021 16:02:56 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > It's a basic limitation of our keyboard input: we can only read from a
> > single frame at a time.
> 
> I guess that'd be difficult to fix...  but could we do something about
> how this works in an emacsclient context?
> 
> That is, if you `M-x' and then change frames in a normal GUI Emacs, the
> `M-x' will follow you around.  There's no such concept in emacsclient as
> an "active frame", but could we somehow make minibuffer commands abort
> the action in other frames?

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.  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"?

bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@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.)

> 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?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: sinoohe.mkh@gmail.com,  9729@debbugs.gnu.org
> Date: Sun, 18 Jul 2021 14:02:51 +0200
> 
> Eli Zaretskii <eliz@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.

bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

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

Isn't there a special handler for `C-g'?  I vaguely seem to recall there
being one...

But I don't know much about this area at all.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no