unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Carlos Pita <carlosjosepita@gmail.com>
To: 37826@debbugs.gnu.org
Subject: bug#37826: Very annoying autoraise client/server behavior with -t option
Date: Sat, 19 Oct 2019 17:46:26 -0300	[thread overview]
Message-ID: <CAELgYhezi4pE6rvYBXOYUpEsynKAFE=ULaiO=_jZ9V8cGamzgQ@mail.gmail.com> (raw)

In client/server mode, if I have a focused client open in a X frame
and then focus a terminal and open a file in that tty in a second
emacs client, the X client is automatically raised and focused (more
precisely, I just get an "emacs is ready" notification because of
gnome/mutter focus stealing prevention). I can go back and forth
between the two clients producing the same effect as many times as
desired.

I understand why this is happening. In server-visit-files:

(let* ((minibuffer-auto-raise (or server-raise-frame
  minibuffer-auto-raise))
...
  (set-buffer (find-file-noselect filen))
...

The problem is that if, for example, I open a bash shell in the tty
buffer, I get a message like "Indentation setup for shell type bash"
in the X minibuffer, so the X frame is autoraised. There are a couple
of issues mixed here, I believe:

1. Maybe the scope of minibuffer-auto-raise = t should be restricted
to the revert/write operations so that focus is not stolen because of
any "accidental" little message.

2. The "Indentation setup for shell type bash" message clearly belongs
to the tty frame but somehow is showing in the other frame. This seems
harder to fix but I'm going to investigate it.

Best regards
--
Carlos





             reply	other threads:[~2019-10-19 20:46 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-19 20:46 Carlos Pita [this message]
2019-10-19 21:39 ` bug#37826: Very annoying autoraise client/server behavior with -t option Carlos Pita
2019-10-20  6:23   ` Eli Zaretskii
2019-10-21  8:58     ` Carlos Pita
2019-10-21 10:22       ` Eli Zaretskii
2019-10-21 13:37         ` Carlos Pita
2019-10-21 13:53           ` Eli Zaretskii
2019-10-21 14:18             ` Carlos Pita
2019-10-21 14:52               ` Carlos Pita
2019-10-21 15:13                 ` Carlos Pita
2019-10-21 16:19                 ` Eli Zaretskii
2019-10-21 16:13               ` Eli Zaretskii
2019-10-21 16:21                 ` Carlos Pita
2019-10-21 16:33                   ` Carlos Pita
2019-10-21 16:39                     ` Eli Zaretskii
2019-10-21 16:37                   ` Eli Zaretskii
2019-10-21 15:56             ` Juanma Barranquero
2019-10-21 16:26               ` Eli Zaretskii
2019-10-21 17:02                 ` Juanma Barranquero
2019-10-21 17:13                   ` Eli Zaretskii
2019-10-21 18:40                     ` Carlos Pita
2019-10-21 20:14                       ` Carlos Pita
2019-10-26 10:57                         ` Eli Zaretskii
2019-10-26 15:53                           ` Carlos Pita
2019-10-26 19:02                             ` Eli Zaretskii
2019-10-26 20:27                               ` Carlos Pita
2019-10-27  5:22                                 ` Eli Zaretskii
2019-10-27  5:45                                   ` Carlos Pita
2019-10-27  6:02                                     ` Eli Zaretskii
2019-10-27 15:04                                       ` Carlos Pita
2019-10-27 15:31                                         ` Eli Zaretskii
2019-10-27 16:31                                           ` Carlos Pita
2019-10-27 16:36                                             ` Eli Zaretskii
2019-10-27 17:02                                               ` Carlos Pita
2019-10-27 17:09                                                 ` Eli Zaretskii
2019-10-27 17:19                                                   ` Carlos Pita
2019-10-27 17:50                                                     ` Eli Zaretskii
2019-11-07 17:23                                                       ` Eli Zaretskii
2020-08-09 16:12                                                         ` Lars Ingebrigtsen
2020-08-09 17:16                                                           ` Eli Zaretskii
2020-08-09 17:26                                                             ` Lars Ingebrigtsen
2019-10-22 14:46                     ` Juanma Barranquero
2019-10-21 13:55           ` Carlos Pita
2019-10-21 13:58             ` Eli Zaretskii
2019-10-20  5:55 ` 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='CAELgYhezi4pE6rvYBXOYUpEsynKAFE=ULaiO=_jZ9V8cGamzgQ@mail.gmail.com' \
    --to=carlosjosepita@gmail.com \
    --cc=37826@debbugs.gnu.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).