GNU bug report logs - #33654
27.0.50; No record of init file errors printed in *Messages*

Previous Next

Full log

Message #20 received at 33654 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: nljlistbox2 <at> gmail.com, 33654 <at> debbugs.gnu.org
Subject: Re: bug#33654: 27.0.50; No record of init file errors printed in
 *Messages*
Date: Sat, 08 Dec 2018 21:24:27 +0200

> Date: Sat, 08 Dec 2018 19:51:47 +0100
> From: martin rudalics <rudalics <at> gmx.at>
> CC: 33654 <at> debbugs.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.

Maybe we could add something to window-setup-hook when we have delayed
warnings to display after startup?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.