From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 20738@debbugs.gnu.org
Subject: bug#20738: 25.0.50; grep/compilation output sometimes has text prop `compilation-message' on final line
Date: Fri, 21 Aug 2020 15:29:09 +0000 (UTC) [thread overview]
Message-ID: <11132197-46a1-4ea4-9add-1f4494cfeb13@default> (raw)
In-Reply-To: <87mu2o8dbn.fsf@gnus.org>
> >> Do you have a recipe?
> >
> > No.
>
> Then it seems unlikely that we'll make further progress here, and I'm
> closing this bug report.
Dunno how you figure that it's unlikely. I said,
at the outset:
It happens sometimes and not other times, but it's not
clear to me what the criteria are.
Also, I can reproduce it with Emacs versions as far
back as 24.1 (I haven't tried further back. I think
24.1 is maybe when property `compilation-message' was
first introduced anyway.)
The bug exists. I don't have recipe to repro it.
There's no relation between not having a recipe and the
frequency of the problem occurring - zero.
The choices, IMO, are to either (1) leave the bug open,
hoping that at some point someone will find or stumble
upon a recipe or a solution or (2) close it, knowing
that the bug exists.
It's not uncommon for bugs to later get more info and
be solved (#1). Of course, if the real aim is to keep
down the bug count, as opposed to recording bugs in
hopes of fixing them, then #2 can happen.
That sometimes happens in organizations where QA is
judged by the outstanding bug count. (IMHO, that has
no place in free software.)
prev parent reply other threads:[~2020-08-21 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 6:43 bug#20738: 25.0.50; grep/compilation output sometimes has text prop `compilation-message' on final line Drew Adams
2015-06-05 7:20 ` Drew Adams
2020-08-20 17:03 ` Lars Ingebrigtsen
2020-08-20 17:49 ` Drew Adams
2020-08-21 11:10 ` Lars Ingebrigtsen
2020-08-21 15:29 ` Drew Adams [this message]
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=11132197-46a1-4ea4-9add-1f4494cfeb13@default \
--to=drew.adams@oracle.com \
--cc=20738@debbugs.gnu.org \
--cc=larsi@gnus.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).