From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, 51132@debbugs.gnu.org, kevin.legouguec@gmail.com,
jidanni@jidanni.org
Subject: bug#51132: [External] : bug#51132: Make sure user is doubly aware of finished complilations
Date: Mon, 11 Oct 2021 19:31:42 +0300 [thread overview]
Message-ID: <83tuhnplox.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB548896D283EF5592F10FCEA8F3B59@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Mon, 11 Oct 2021 16:21:02 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> CC: "kevin.legouguec@gmail.com" <kevin.legouguec@gmail.com>,
> "larsi@gnus.org"
> <larsi@gnus.org>,
> "51132@debbugs.gnu.org" <51132@debbugs.gnu.org>,
> "jidanni@jidanni.org" <jidanni@jidanni.org>
> Date: Mon, 11 Oct 2021 16:21:02 +0000
>
> > > > > A message is issued, and I think that's sufficient. Closing.
> > > >
> > > > Note that you can customize compilation-finish-functions
> > > > to do all sorts of things; you can e.g. send a desktop
> > > > notification:
> > >
> > > Fine. But by default Emacs should generally pair
> > > notification of starting/continuing progress with
> > > notification of finishing - in the _same manner_,
> > > at a minimum.
> >
> > It does. PLEASE try this before you post.
>
> PLEASE read what I wrote. I replied to a claim
> that it's sufficient to issue a message, to end
> a mode-line in-progress message.
How is it useful to ask for something that already happens? Even if
Lars didn't mention it? It just adds noise.
> Whether there is in fact such a lack/bug is
> something else.
Please make a point of looking at the actual behavior before you join
a discussion. If you want to help the discussion to be constructive.
next prev parent reply other threads:[~2021-10-11 16:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 6:50 bug#51132: Make sure user is doubly aware of finished complilations 積丹尼 Dan Jacobson
2021-10-11 8:46 ` Lars Ingebrigtsen
2021-10-11 9:21 ` Kévin Le Gouguec
2021-10-11 14:44 ` bug#51132: [External] : " Drew Adams
2021-10-11 16:03 ` Eli Zaretskii
2021-10-11 16:21 ` Drew Adams
2021-10-11 16:31 ` Eli Zaretskii [this message]
2021-10-11 16:44 ` Drew Adams
2021-10-12 8:01 ` 積丹尼 Dan Jacobson
2021-10-12 13:59 ` Eli Zaretskii
2021-10-11 14:41 ` Drew Adams
2021-10-11 16:03 ` Eli Zaretskii
2021-10-11 16:13 ` Drew Adams
2021-10-11 12:16 ` Eli Zaretskii
2021-10-12 8:04 ` 積丹尼 Dan Jacobson
2021-10-12 14:00 ` Eli Zaretskii
2021-10-12 15:16 ` Kévin Le Gouguec
2021-10-12 16:11 ` Eli Zaretskii
2021-10-12 18:24 ` Kévin Le Gouguec
2021-10-20 1:09 ` 積丹尼 Dan Jacobson
2021-10-20 6:09 ` Kévin Le Gouguec
2021-10-22 12:32 ` 積丹尼 Dan Jacobson
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=83tuhnplox.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51132@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=jidanni@jidanni.org \
--cc=kevin.legouguec@gmail.com \
--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).