From: Carlos Pita <carlosjosepita@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, 37826@debbugs.gnu.org
Subject: bug#37826: Very annoying autoraise client/server behavior with -t option
Date: Sat, 26 Oct 2019 12:53:30 -0300 [thread overview]
Message-ID: <CAELgYhcveUZ8bR=4aMFbbOQ2XB6JGCCwEuyM_VScwQ9ty9Fipw@mail.gmail.com> (raw)
In-Reply-To: <83ftjfvkov.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
>
>
>
> We generally prefer not to use advice-add etc. in our own code. What
> I had in mind was to modify the places where such messages originate,
> and make them use delay-message under the right circumstances. If
> there's some mechanism to do this without changing each place, I'm
> okay with that, but using advice is not one of them.
>
Besides monkey-patching the message function in an even dirtier way, I
don't think that would be possible. I don't have the time nor the energy to
review every possible module that is messaging during startup. I could add
an option for message to redirect its messages to some other place, but I
don't see any advantage in doing so.
>
FWIW, I cannot reproduce this on my system. In fact, I cannot even
> reproduce your original reported issue with visiting a
> shell-scrip-mode file: I get a new frame with the message, and no old
> frame is raised. Are you using something other than "emacsclient -c"?
>
emacsclient -c
Then opening my .bashrc with
emacsclient -t
Raises the first frame.
The daemon was launched with -Q.
[-- Attachment #2: Type: text/html, Size: 1954 bytes --]
next prev parent reply other threads:[~2019-10-26 15:53 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
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 [this message]
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='CAELgYhcveUZ8bR=4aMFbbOQ2XB6JGCCwEuyM_VScwQ9ty9Fipw@mail.gmail.com' \
--to=carlosjosepita@gmail.com \
--cc=37826@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lekktu@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).