Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!tut.cis.ohio-state.edu!EW09.NAS.NASA.GOV!raible
From: raible@EW09.NAS.NASA.GOV (Eric L. Raible)
Newsgroups: gnu.emacs.bug
Subject: bug in minibuffer-complete
Message-ID: <8907191913.AA00889@ew09.nas.nasa.gov>
Date: 19 Jul 89 19:13:18 GMT
References: <8907191806.AA01267@ketchum.uswest.com>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: raible@orville.nas.nasa.gov
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 18


   Date: Wed, 19 Jul 89 12:06:18 MDT
   From: Joe Wells <jbw@uswest.com>

   Not really a bug, more of a subtle interation problem.  When you use
   message, the contents of the message are displayed instead of the contents
   of the minibuffer.  The "[no match]" message is implemented by modifying
   the contents of the minibuffer temporarily.  In your case, by the time the
   message stops being displayed, the minibuffer contents have been restored,
   so you don't see the "[no match]".  If you wanted, you could modify the
   function that displays the "[no match]" and make it clear out the message
   buffer so that the minibuffer contents are displayed.  (That by itself is
   quite a trick from lisp, took me a long time to figure out.)

You might call this a "subtle interation problem", but I call it a
subtle bug.

Regardless of the reasons behind it, this is undesirable behavior.