From: Oleh Krehel <ohwoeowho@gmail.com>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Is there a way to inhibit message3 from Elisp?
Date: Wed, 22 Apr 2015 19:20:37 +0200 [thread overview]
Message-ID: <87sibsyt96.fsf@gmail.com> (raw)
In-Reply-To: <CAAdUY-Jf=gKgnE33WW4oKu2o27pAomi0PjO9Jj2bCryo=vR1EQ@mail.gmail.com> (Artur Malabarba's message of "Wed, 22 Apr 2015 18:22:11 +0100")
Artur Malabarba <bruce.connor.am@gmail.com> writes:
>> Updated etc/NEWS and the manual (entry for `message').
>> Let me know if it's OK to merge.
>
> Now that I think about it, the really ideal way to do this would be to
> have a with-no-messages macro/special form, so that stupid packages
> can't setq this variable permanently.
>
> But if that's too impractical, the current version is fine.
I'm not sure if it's possible or practical. message3 is in C, so there
would need to be an Elisp variable that connects the macro and the C
code.
In any case, there's already a good way to deal with stupid packages.
Oleh
next prev parent reply other threads:[~2015-04-22 17:20 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
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 [this message]
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=87sibsyt96.fsf@gmail.com \
--to=ohwoeowho@gmail.com \
--cc=bruce.connor.am@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).