unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: sinoohe.mkh@gmail.com, 9729@debbugs.gnu.org
Subject: bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files
Date: Fri, 16 Jul 2021 18:28:35 +0300	[thread overview]
Message-ID: <83v95a46sc.fsf@gnu.org> (raw)
In-Reply-To: <87mtqm72c7.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri,  16 Jul 2021 16:36:24 +0200)

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





  reply	other threads:[~2021-07-16 15:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11  8:28 bug#9729: 24.0.50; can't editing buffers while in another buffer i'm openning files sinoohe.mkh
2011-10-11 17:50 ` Glenn Morris
2011-10-12  5:43   ` mehran khajavi
2021-07-16 14:36 ` Lars Ingebrigtsen
2021-07-16 15:28   ` Eli Zaretskii [this message]
2021-07-17 14:02     ` Lars Ingebrigtsen
2021-07-17 15:17       ` Eli Zaretskii
2021-07-18 12:02         ` Lars Ingebrigtsen
2021-07-18 12:37           ` Eli Zaretskii
2021-07-18 13:03             ` Lars Ingebrigtsen

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=83v95a46sc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=9729@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=sinoohe.mkh@gmail.com \
    /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).