unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Oleh Krehel <ohwoeowho@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Is there a way to inhibit message3 from Elisp?
Date: Wed, 22 Apr 2015 13:55:42 +0200	[thread overview]
Message-ID: <87lhhke5s1.fsf@gmail.com> (raw)
In-Reply-To: <83618o4eom.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 22 Apr 2015 13:53:29 +0300")

Eli Zaretskii <eliz@gnu.org> writes:
>> I got this code to work as I expect:
>> 
>> (progn
>>   (setq inhibit-message t)
>>   (message "foo")
>>   (setq inhibit-message nil))
>> 
>> However, this doesn't work:
>> 
>> (let ((inhibit-message t))
>>   (message "foo"))
>
> How does it "not work"?  It did for me.

I misunderstood that when "C-x C-e" would not print the message in
*scratch*. But otherwise, it works.

> Some comments for the changes:
>
>   . This variable is a boolean, so it's better to use DEFVAR_BOOL
>     instead of DEFVAR_LISP.  (Don't forget to change the test in
>     message3 accordingly.)
>
>   . The Emacs coding conventions are to use this:
>
>       if (something)
>         {
> 	  do_whatever ();
> 	}
>
>     rather than this:
>
>       if (something) {
>         do_whatever ();
>       }
>
>     Besides, when there's only one statement after 'if', you don't
>     need the braces at all.

OK.

>   . With your last change, the doc string is misleading, and should be
>     updated.

Updated.

>   . The change should be accompanied by an entry in etc/NEWS.  Bonus
>     points for updating the ELisp manual as well.

Updated etc/NEWS and the manual (entry for `message').
Let me know if it's OK to merge.

Oleh







  reply	other threads:[~2015-04-22 11:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 13:37 Is there a way to inhibit message3 from Elisp? Oleh Krehel
2015-04-21 17:17 ` Stefan Monnier
2015-04-21 18:50   ` Oleh Krehel
2015-04-21 23:25     ` Artur Malabarba
2015-04-22  6:00       ` Oleh Krehel
2015-04-22 10:53     ` Eli Zaretskii
2015-04-22 11:55       ` Oleh Krehel [this message]
2015-04-22 12:24         ` Eli Zaretskii
2015-04-22 12:50           ` Oleh Krehel
2015-04-22 13:01             ` Eli Zaretskii
2015-04-22 13:51           ` Stefan Monnier
2015-04-22 13:48             ` Oleh Krehel
2015-04-22 17:39             ` Artur Malabarba
2015-04-22 20:20               ` Stefan Monnier
2015-04-22 12:42         ` Artur Malabarba
2015-04-22 17:22         ` Artur Malabarba
2015-04-22 17:20           ` Oleh Krehel
2015-04-22 13:53     ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87lhhke5s1.fsf@gmail.com \
    --to=ohwoeowho@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).