From: Hong Xu <hong@topbug.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24861@debbugs.gnu.org
Subject: bug#24861: [PATCH] Fix annoying "Parsing...done" message in c++-mode
Date: Tue, 15 Nov 2016 16:03:19 -0800 [thread overview]
Message-ID: <877f84mgu0.fsf@topbug.net> (raw)
In-Reply-To: <87a8dgo13q.fsf@topbug.net>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
On 2016-11-03 Thu 11:43 GMT-0800, Hong Xu <hong@topbug.net> wrote:
> On 2016-11-03 Thu 11:15 GMT-0700, Eli Zaretskii <eliz@gnu.org> wrote:
>
>>> 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?
>
> It was not me who singled out this particular package; it was singled
> out before, with the frequency hard coded to be 1 second. I just made it
> more flexible and correct a misused plain `message'.
>
>>
>> Also, what useful information does it conceal? Can you show a use
>> case where this happens?
>
> I've never seen how these information can be useful (ideally I would say
> concealing all these cpp-progress-message unless some debug option is
> turned on), but I'm probably not qualified enough to make such
> assertion.
>
> One annoying case is that I've set up to show the syntax error at point,
> but the "Parsing...done" message frequently comes in the way before I
> can read the message.
Can you still consider this patch?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-11-16 0:03 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
2016-11-03 18:43 ` Hong Xu
2016-11-16 0:03 ` Hong Xu [this message]
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
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=877f84mgu0.fsf@topbug.net \
--to=hong@topbug.net \
--cc=24861@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).