Re: Annoying paren match messages in minibuffer

[Dan Nicolaescu]

Miles Bader <address@hidden> writes:

  > Stefan Monnier <address@hidden> writes:
  > > Maybe the problem can be fixed by changing the way the message is
  > > displayed.  E.g. it could be displayed as " [unmatched paren]" at the
  > > end of the minibuffer input, as is done for minibuffer
  > > completion messages.
  > 
  > I think all messages should be.  I've used experimental code to do that
  > in the past, and it was _really_ nice.  No stupid awkward pauses and
  > annoyance like the current method, everything just seemed *right*.

How about allowing the minibuffer to have a header line, and display
messages in the header line?  This limits the messages to be one line
long, but it's probably easier to read, and it shouldn't be too much of
a distraction.  Just my 2 cents.