all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Hong Xu <hong@topbug.net>
Cc: 24861@debbugs.gnu.org
Subject: bug#24861: [PATCH] Fix annoying "Parsing...done" message in c++-mode
Date: Thu, 03 Nov 2016 20:15:03 +0200	[thread overview]
Message-ID: <831sysmnvc.fsf@gnu.org> (raw)
In-Reply-To: <87pomdihhd.fsf@topbug.net> (message from Hong Xu on Wed, 02 Nov 2016 16:34:22 -0700)

> From: Hong Xu <hong@topbug.net>
> Cc: 24861@debbugs.gnu.org
> Cc: Andreas Schwab <schwab@linux-m68k.org>
> Date: Wed, 02 Nov 2016 16:34:22 -0700
> 
> On 2016-11-02 Wed 13:21 GMT-0700, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> > (Not that I understand why this particular message needs to be
> > customizable.)
> 
> Because the messages by cpp.el is so frequent that it often competes
> with other useful information.

Yes, but we have lots of similar messages in other places.  A search
for a call to 'message' that displays "SOMETHING...done" turns up more
than 270 hits.  Why is this particular package being singled out?

Also, what useful information does it conceal?  Can you show a use
case where this happens?

> I've added some explanation in the docstring.

That should not be necessary, such explanations should be in comments
and commit log messages.

Thanks.





  reply	other threads:[~2016-11-03 18:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 18:45 bug#24861: [PATCH] Fix annoying "Parsing...done" message in c++-mode Hong Xu
2016-11-02 20:09 ` Hong Xu
2016-11-02 20:21   ` Eli Zaretskii
2016-11-02 23:34     ` Hong Xu
2016-11-03 18:15       ` Eli Zaretskii [this message]
2016-11-03 18:43         ` Hong Xu
2016-11-16  0:03           ` Hong Xu
2016-11-18  9:39             ` Eli Zaretskii
2016-11-18 19:55               ` Hong Xu
2016-11-19  7:50                 ` Eli Zaretskii
2016-11-20  0:20                   ` Hong Xu
2016-11-25 10:53                     ` Eli Zaretskii
2016-11-02 23:39     ` Hong Xu
2016-11-03 16:39     ` Richard Stallman
2016-11-02 22:05   ` Andreas Schwab

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=831sysmnvc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24861@debbugs.gnu.org \
    --cc=hong@topbug.net \
    /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.