From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: 30397@debbugs.gnu.org, Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#30397: Random numbers in grep mode-line
Date: Sun, 11 Feb 2018 20:54:52 -0800 (PST) [thread overview]
Message-ID: <92b33e1f-f133-4ad1-9bda-4d40353db19a@default> (raw)
In-Reply-To: <87h8qnb3yi.fsf@mail.linkov.net>
> > Is the total number of lines (in the search space) also
> > available? If so, would that be useful? Maybe something
> > like this?
> >
> > Grep finished at Thu Jul 21 15:02:15 - 42 matches in 5/113 lines
> > ^^^^
>
> Unfortunately the total number of lines is not available.
> There is even problems with getting the right number of matches.
> When grep doesn't highlight matches, we can't count them.
In that case, the explanation/description should say that
it is the number of matches highlighted, not the number
of matches.
> Another problem is that grep matches to be printed at the end of the
> grep buffer can't be counted in grep-regexp-alist because it is
> based on font-lock which is invoked at unpredictable times
> when grep process is already finished. This leaves only one way
> to count matches in grep-filter in this patch.
>
> For the same reason, printing the number of compilation errors at
> the end of the compilation buffer can't be implemented for bug#13417.
If the numbers shown depend on font-lock and are not
necessarily accurate then the doc should make that
clear.
next prev parent reply other threads:[~2018-02-12 4:54 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92b33e1f-f133-4ad1-9bda-4d40353db19a@default \
--to=drew.adams@oracle.com \
--cc=30397@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=npostavs@users.sourceforge.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.