GNU bug report logs - #3579
23.0.94; Customize: Cannot see error messages if use standalone minibuffer

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 3579 in the body.
You can then email your comments to 3579 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: "Drew Adams" <drew.adams <at> oracle.com>
To: <emacs-pretest-bug <at> gnu.org>
Subject: 23.0.94; Customize: Cannot see error messages if use standalone minibuffer
Date: Mon, 15 Jun 2009 10:11:36 -0700

Can't give a great recipe for this - you have to set up Emacs to use a
standalone minibuffer (separate frame) only. That's all you need to
do, I believe, to reproduce it.
 
Edit an option value to make it invalid - e.g. edit an integer field
to be 2.5. Then choose Set for Current Session in the State menu.  You
will not see an error message in the minibuffer frame (which is where
the echo area is), or anywhere else. The message does get logged to
*Messages*, but the user gets no feedback at all.
 
Note that mouseover messages appear fine in the echo area.  E.g. turn
off tooltip-mode and put the mouse over the State button. You will see
the text in the echo area. Likewise, other Emacs messages, as produced
by `message' and `error', for instance, appear fine in the echo
area. It is only Customize messages that do not appear anywhere.
 
 
 
In GNU Emacs 23.0.94.1 (i386-mingw-nt5.1.2600)
 of 2009-05-24 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'
 

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: "Drew Adams" <drew.adams <at> oracle.com>
Cc: 3579 <at> debbugs.gnu.org
Subject: Re: bug#3579: 23.0.94;
 Customize: Cannot see error messages if use standalone minibuffer
Date: Sun, 09 Feb 2014 21:21:32 -0800

"Drew Adams" <drew.adams <at> oracle.com> writes:

> Can't give a great recipe for this - you have to set up Emacs to use a
> standalone minibuffer (separate frame) only. That's all you need to
> do, I believe, to reproduce it.
>
> Edit an option value to make it invalid - e.g. edit an integer field
> to be 2.5. Then choose Set for Current Session in the State menu.  You
> will not see an error message in the minibuffer frame (which is where
> the echo area is), or anywhere else. The message does get logged to
> *Messages*, but the user gets no feedback at all.
>
> Note that mouseover messages appear fine in the echo area.  E.g. turn
> off tooltip-mode and put the mouse over the State button. You will see
> the text in the echo area. Likewise, other Emacs messages, as produced
> by `message' and `error', for instance, appear fine in the echo
> area. It is only Customize messages that do not appear anywhere.

This was four years ago.  Are you still seeing this problem?

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

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

From: Drew Adams <drew.adams <at> oracle.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 3579 <at> debbugs.gnu.org
Subject: RE: bug#3579: 23.0.94; Customize: Cannot see error messages if use
 standalone minibuffer
Date: Sun, 9 Feb 2014 21:47:09 -0800 (PST)

> This was four years ago.  Are you still seeing this problem?

Yes (but see below).

What actually happens (I might not have been aware of this
when I sent the report) is that the error message flashes in the
echo area very briefly, but it is immediately replaced by the
previous echo area contents, which might be a message, such as
`Back to top level' or it might be blank space (perhaps from
a call such as (message nil)?).

IOW, I think the problem is that the error message is transient,
and far too brief.  There is no reason to restore whatever
echo-area contents were there before.

With emacs -Q the error message remains.  It seems there is
something in my setup, besides just useing a standalong
minibuffer, that causes this.  I will try to bisect the code
later to see if I can narrow it down.  You can close this
bug, please.  If I narrow it down and find an Emacs bug I'll
report it.  Thx.

Previous Next

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