GNU bug report logs - #64165
‘minibuffer-message’: naming/documentation bug

Previous Next

Full log

View this message in rfc822 format

From: Shynur Xie <one.last.kiss <at> outlook.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "64165 <at> debbugs.gnu.org" <64165 <at> debbugs.gnu.org>
Subject: bug#64165: ‘minibuffer-message’: naming/documentation bug
Date: Mon, 19 Jun 2023 17:43:04 +0000

> From: Eli Zaretskii
> Date: Mon, 19 Jun 2023 20:12:42 +0300
>   To: Shynur
>
> If I need to guess the issue which confused you,

The issue that's bothering me is that both the name and documentation of
‘minibuffer-message’ says that ‘minibuffer-message’ uses minibuffer,
but after adding

    (lambda ()
      (display-fill-column-indicator-mode -1))

to ‘minibuffer-mode-hook’, then executing

    (minibuffer-message "Message Line 1\nMessage Line 2")

I can still see the fill column indicator:

    Message Line 1                  │
    Message Line 2
                                    ^ fill column indicator here

> will it help saying in the doc string that 'minibuffer-message'
> works like 'message' when the current buffer is not the minibuffer?

I simply don’t know whether ‘minibuffer-message’ works like ‘message’
when the current buffer is not the minibuffer; I'm not familiar with
how ‘minibuffer’ works.

I think if the documentation directly states: “message is shown in
echo area when the current buffer is not minibuffe” (if indeed this is
the case), it would clarify a lot.

Previous Next

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