all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 30397@debbugs.gnu.org
Subject: bug#30397: Random numbers in grep mode-line
Date: Sat, 10 Feb 2018 23:32:44 +0200	[thread overview]
Message-ID: <87zi4gpm2r.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAM-tV--PZ-4EJBieRttoM11XWFa3n0jWeGKi5puoJ8j6h8jY1g@mail.gmail.com> (Noam Postavsky's message of "Thu, 8 Feb 2018 18:00:39 -0500")

>> What was the goal of this feature and where it is documented?
>
> `(emacs) Compilation' (and similar in etc/NEWS):
>
>       While compilation proceeds, the mode line is updated to show the
>     number of errors, warnings, and informational messages that have been
>     seen so far.
>
> Perhaps it needs some adjustment for grep.
>
> Original report: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25354

Yes, some adjustment is needed for grep.  That reminded me
about two unclosed feature requests: bug#13417 and bug#14017
that proposed to display these numbers also at the bottom of
output buffers.  But the showstopper was to decide on the
final format of such messages.  Although this looks good:

  Grep finished with 42 matches in 5 lines at Thu Jul 21 15:02:15

Than the mode-line will display two numbers: the number of matches
and the number of matching lines (in green).





  reply	other threads:[~2018-02-10 21:32 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zi4gpm2r.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=30397@debbugs.gnu.org \
    --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.