unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, 30397@debbugs.gnu.org
Subject: bug#30397: Random numbers in grep mode-line
Date: Thu, 8 Feb 2018 13:48:55 -0800 (PST)	[thread overview]
Message-ID: <702f1621-529b-47b0-a15d-898a2fd81f79@default> (raw)
In-Reply-To: <87tvurtbek.fsf@mail.linkov.net>

> What do these seemingly random numbers in the mode-line of the *grep*
> buffer mean?  I don't get any logic behind these colored numbers.
> They are neither the number of matches nor the number of matched lines.
> And why non-zero numbers are always highlighted in red as errors
> when there are no errors in the grep output?  What was the goal
> of this feature and where it is documented?

+1.

A mouseover tooltip says this:

1. Number of errors so far
2. Number of warnings so far
3. Number of informational messages so far

But `C-h m' says nothing about this (it should).

And clicking `compilation-mode' (the parent) in the `C-h m' output
shows that mode's doc, but it too says nothing about this.





  reply	other threads:[~2018-02-08 21:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 21:32 bug#30397: Random numbers in grep mode-line Juri Linkov
2018-02-08 21:48 ` Drew Adams [this message]
2018-02-09  9:51   ` Eli Zaretskii
2018-02-08 23:00 ` Noam Postavsky
2018-02-10 21:32   ` Juri Linkov
2018-02-10 22:01     ` Drew Adams
2018-02-11 21:40       ` Juri Linkov
2018-02-12  4:54         ` Drew Adams
2018-02-12 15:47         ` Eli Zaretskii
2018-02-12 21:39           ` Juri Linkov
2018-02-11 20:45     ` Richard Stallman
2018-02-12 16:34       ` Eli Zaretskii
2018-02-09  9:50 ` Eli Zaretskii
     [not found] <<87tvurtbek.fsf@mail.linkov.net>
     [not found] ` <<702f1621-529b-47b0-a15d-898a2fd81f79@default>
     [not found]   ` <<83eflu4hjx.fsf@gnu.org>
2018-02-09 15:27     ` Drew Adams
2018-02-09 15:35       ` Eli Zaretskii
     [not found] ` <<83fu6a4hlh.fsf@gnu.org>
2018-02-09 15:43   ` Drew Adams
     [not found] <<<87tvurtbek.fsf@mail.linkov.net>
     [not found] ` <<<702f1621-529b-47b0-a15d-898a2fd81f79@default>
     [not found]   ` <<<83eflu4hjx.fsf@gnu.org>
     [not found]     ` <<3e9d0fd8-b859-4eec-8f34-54185dd6c0f3@default>
     [not found]       ` <<83zi4i2n2o.fsf@gnu.org>
2018-02-09 15:59         ` Drew Adams

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=702f1621-529b-47b0-a15d-898a2fd81f79@default \
    --to=drew.adams@oracle.com \
    --cc=30397@debbugs.gnu.org \
    --cc=juri@linkov.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 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).