From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: carlosjosepita@gmail.com, 37826@debbugs.gnu.org
Subject: bug#37826: Very annoying autoraise client/server behavior with -t option
Date: Mon, 21 Oct 2019 20:13:55 +0300 [thread overview]
Message-ID: <83r23610oc.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SSmGxWpguAMJOiN1=fV=-TS0XBPMT1C9Hi608Liw8pKyg@mail.gmail.com> (message from Juanma Barranquero on Mon, 21 Oct 2019 19:02:42 +0200)
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 21 Oct 2019 19:02:42 +0200
> Cc: carlosjosepita@gmail.com, 37826@debbugs.gnu.org
>
> diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi
> index 82d9f1db61..7ea582d012 100644
> --- a/doc/lispref/display.texi
> +++ b/doc/lispref/display.texi
> @@ -870,6 +870,12 @@ Delayed Warnings
> @code{delayed-warnings-list} to @code{nil}.
> @end defvar
>
> +@defun delay-warning type message &optional level buffer-name
> +This function is the delayed counterpart to @code{display-warning},
> +and it is called with the same arguments. The warning message is
> +queued into @code{delayed-warnings-list}.
> +@end defun
> +
> @node Invisible Text
> @section Invisible Text
Thanks. I think this should go before the description of
delayed-warnings-list, and the text at the beginning of the section
should be modifies to mention this function as another alternative to
queue warnings for delayed display.
next prev parent reply other threads:[~2019-10-21 17: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
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 [this message]
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=83r23610oc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37826@debbugs.gnu.org \
--cc=carlosjosepita@gmail.com \
--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).