From: Eli Zaretskii <eliz@gnu.org>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: 37826@debbugs.gnu.org
Subject: bug#37826: Very annoying autoraise client/server behavior with -t option
Date: Mon, 21 Oct 2019 19:13:19 +0300 [thread overview]
Message-ID: <834l022i1s.fsf@gnu.org> (raw)
In-Reply-To: <CAELgYhcLkmTFHPkYJNmq2uF+5TsJajQ2NjUdP+g4yabOffo6+Q@mail.gmail.com> (message from Carlos Pita on Mon, 21 Oct 2019 11:18:04 -0300)
> From: Carlos Pita <carlosjosepita@gmail.com>
> Date: Mon, 21 Oct 2019 11:18:04 -0300
> Cc: 37826@debbugs.gnu.org
>
> >
> > > And how to know when to delay/ignore and when to show if there is no
> > > priority hint?
> >
> > I think this is pretty clear: we want to delay when a shell script is
> > visited via the client.
>
> I didn't mean what common sense would tell us in each case, but how to
> codify that in rules that don't quickly become a long list of patterns
> always missing some case (and then there are non-builtin packages...).
Maybe I don't understand what you are asking. The important part of
my answer is "visited via the client", so I'm not sure what is hard in
that rule.
> > In that case, we visit the file in an existing frame. By contrast,
> > the client needs to create a frame, and if it does that before
> > visiting the file, it will momentarily show some other buffer in that
> > frame.
> > [...]
> > No, because it will flash an empty buffer, something that Emacs
> doesn't do.
>
> I don't get this, in both cases we have a frame that is created and a
> file that is visited. The client has the extra possibility of
> pre-loading the buffer without selecting it, which you have exploited.
> But standalone emacs has to show something before.
No, it shows the visited file immediately.
> I'm checking that right now and it indeed shows a blank screen
> (plenty of "flashes" while resizing, hiding bars, etc).
That "empty screen" is really empty, i.e. it's a window created by the
windowing system, and Emacs didn't yet display anything there. Your
suggestion would show a buffer, with its mode line and other
decorations. That's what the change you are talking about wanted to
avoid.
> Isn't "blank -> desired buffer" much better than "random visited
> buffer -> desired buffer" in terms of flashing? Could we give that a
> try?
I'd like to try cleaner solutions first, okay?
> I certainly don't see the current focus stealing behavior as cosmetic
> or minor
But it happens only in a small number of major modes, right? Until
now, you identified just one: shell-script mode. Are there others?
next prev parent reply other threads:[~2019-10-21 16:13 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 20:46 bug#37826: Very annoying autoraise client/server behavior with -t option Carlos Pita
2019-10-19 21:39 ` 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 [this message]
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=834l022i1s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37826@debbugs.gnu.org \
--cc=carlosjosepita@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).