all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 20445 <20445@debbugs.gnu.org>
Subject: bug#20445: excessive redisplay / echo area resizing during byte-compilation
Date: Wed, 29 Apr 2015 09:58:19 +0100	[thread overview]
Message-ID: <CAAdUY-KND4mJzDvxjQJZrw2Zrd8MmJSe_eQXH6ZVGDs4Jc6jew@mail.gmail.com> (raw)
In-Reply-To: <CAAdUY-+FHgZF59vP0PiR3AoSgtB=BNWqyXeFhQ2m_RoDAhpcgg@mail.gmail.com>

Actually, if we're going to make it so that the caller needs to
explicitly silence the compiler, then we might as well just revert to
the old behavior (no silencing) and let the caller use
`inhibit-messages' himself instead of defining a new bytecomp-specific
variable.





  reply	other threads:[~2015-04-29  8:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 21:31 bug#20445: excessive redisplay / echo area resizing during byte-compilation Glenn Morris
2015-04-27 21:44 ` Glenn Morris
2015-04-28  9:33 ` martin rudalics
2015-04-28 14:26   ` martin rudalics
2015-04-28 15:22     ` Eli Zaretskii
2015-04-28 17:43       ` martin rudalics
2015-04-28 18:00         ` Eli Zaretskii
2015-04-29  7:11           ` martin rudalics
2015-04-28 15:13 ` Eli Zaretskii
2015-04-29  3:21   ` Stefan Monnier
2015-04-29  7:11     ` martin rudalics
2015-04-29  8:56       ` Artur Malabarba
2015-04-29  8:58         ` Artur Malabarba [this message]
2015-04-29  7:37     ` Artur Malabarba
2015-04-29 15:53     ` Eli Zaretskii
2015-04-29 18:35       ` Artur Malabarba
2015-04-29 18:52         ` Artur Malabarba
2015-05-01 10:41           ` martin rudalics
2015-05-01 12:20             ` Artur Malabarba
2015-05-01 13:45               ` martin rudalics
2015-05-01 14:19                 ` Artur Malabarba
2015-05-01 16:28                   ` Artur Malabarba
2015-05-02  8:58                   ` martin rudalics
2015-05-01 10:41         ` martin rudalics

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=CAAdUY-KND4mJzDvxjQJZrw2Zrd8MmJSe_eQXH6ZVGDs4Jc6jew@mail.gmail.com \
    --to=bruce.connor.am@gmail.com \
    --cc=20445@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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.