unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>, "N. Jackson" <nljlistbox2@gmail.com>
Cc: 33654@debbugs.gnu.org
Subject: bug#33654: 27.0.50; No record of init file errors printed in *Messages*
Date: Sat, 08 Dec 2018 19:51:47 +0100	[thread overview]
Message-ID: <5C0C12C3.4060603@gmx.at> (raw)
In-Reply-To: <83wook47pe.fsf@gnu.org>

 > I'm not sure we can guarantee that the frame showing *Warnings* is
 > always on top, since user initialization can create any number of
 > frames.

In general we cannot guarantee that for any frame when there are
several of them.  Usually, the last frame created is the one on top.

A user could add a function to 'window-setup-hook' which looks whether
a *Warnings* buffer exists and, if it is not shown on the selected
frame, display it there and maybe delete it elsewhere.  Or, obviously,
select the frame where it is shown.  I don't know whether it's a good
idea to do that automatically.

martin





  reply	other threads:[~2018-12-08 18:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07  0:42 bug#33654: 27.0.50; No record of init file errors printed in *Messages* N. Jackson
2018-12-07  7:13 ` Eli Zaretskii
2018-12-07 17:08   ` N. Jackson
2018-12-08 10:46     ` Eli Zaretskii
2018-12-08 18:51       ` martin rudalics [this message]
2018-12-08 19:24         ` Eli Zaretskii
2018-12-09  8:26           ` martin rudalics
2020-10-11  1:54             ` Lars Ingebrigtsen
2021-05-11 13:49               ` 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=5C0C12C3.4060603@gmx.at \
    --to=rudalics@gmx.at \
    --cc=33654@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=nljlistbox2@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).