all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 3579@debbugs.gnu.org
Subject: bug#3579: 23.0.94; Customize: Cannot see error messages if use standalone minibuffer
Date: Sun, 09 Feb 2014 21:21:32 -0800	[thread overview]
Message-ID: <87wqh37db7.fsf@building.gnus.org> (raw)
In-Reply-To: <769A36CCB7F24081932EDA6DDE69C4D5@us.oracle.com> (Drew Adams's message of "Mon, 15 Jun 2009 10:11:36 -0700")

"Drew Adams" <drew.adams@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/





  reply	other threads:[~2014-02-10  5:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 17:11 bug#3579: 23.0.94; Customize: Cannot see error messages if use standalone minibuffer Drew Adams
2014-02-10  5:21 ` Lars Ingebrigtsen [this message]
2014-02-10  5:47   ` Drew Adams

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wqh37db7.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --cc=3579@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.