From: Christian Schwarzgruber <c.schwarzgruber.cs@gmail.com>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 31627@debbugs.gnu.org
Subject: bug#31627: 27.0.50; isearch prompt not shown when `inhibit-message` is set to `t`
Date: Tue, 29 May 2018 07:37:37 +0200 [thread overview]
Message-ID: <87efhvowda.fsf@gmail.com> (raw)
In-Reply-To: <874lirxcq4.fsf@gmail.com>
Thank you for clarification!
With that "docstring" things are now clear to me.
-Christian
Tino Calancha <tino.calancha@gmail.com> writes:
> Christian Schwarzgruber <c.schwarzgruber.cs@gmail.com> writes:
>
>> Hello Everybody!
>>
>> (setq inhibit-message t) hides isearch prompt. Is this defined behavior
>> or a bug?
> Its use is not intended to be set globally by users, because you don't
> want to suppress all the calls to `message'; `message' is a common way
> for Emacs to talk with its users, ask them for input or whatever.
> Maybe something could be added in its docstring to make the point clear.
>
> This var is mainly used by package developers in a controlled way:
> typically by locally let-binding it around an expression. For example,
> imagine the package `foo' having an user option
> `foo-verbose' to display/suppress not very important messages:
>
> (defcustom foo-verbose t
> "If nil, suppress some messages"
> :type 'boolean
> :group 'foo)
>
> (defun foo-set-vars ()
> (message "Setting package variables!")
> (setq foo-mint 100)
> (setq foo-star -1))
>
> (defun foo-start ()
> (foo-procastinate-response)
> (message "Initialisation complete!"))
>
> (defun foo-initialize ()
> (let ((inhibit-message (not verbose)))
> (foo-set-vars)
> (foo-start)))
>
> That would be OK.
> Another typical use is to suppress garbage messages
> when writing tests.
next prev parent reply other threads:[~2018-05-29 5:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 15:20 bug#31627: 27.0.50; isearch prompt not shown when `inhibit-message` is set to `t` Christian Schwarzgruber
2018-05-28 16:01 ` Robert Pluim
2018-05-29 5:17 ` Tino Calancha
2018-05-29 5:37 ` Christian Schwarzgruber [this message]
2018-06-02 11:10 ` Eli Zaretskii
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=87efhvowda.fsf@gmail.com \
--to=c.schwarzgruber.cs@gmail.com \
--cc=31627@debbugs.gnu.org \
--cc=tino.calancha@gmail.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.