From: Stefan Kangas <stefankangas@gmail.com>
To: Dan Jacobson <jidanni@jidanni.org>
Cc: 59269@debbugs.gnu.org
Subject: bug#59269: Maybe add timestamps to *Async-native-compile-log* by default
Date: Thu, 24 Nov 2022 16:55:00 -0800 [thread overview]
Message-ID: <CADwFkmmAbYi-zan0M=3us=FukZoswuoLeLvGVAw7oCie2eHmHw@mail.gmail.com> (raw)
In-Reply-To: <87fsehbzh5.8.fsf@jidanni.org> (Dan Jacobson's message of "Thu, 17 Nov 2022 05:19:02 -0600")
tags 59269 + wontfix
close 59269
thanks
Dan Jacobson <jidanni@jidanni.org> writes:
> I'm just saying at first glance it looks like something looping because
> there are 145 identical line
>>> $ sort|uniq -c|sort -nr
>>> 145 Loading debian-ispell...
>>> 145 Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)...
>
> But OK, each time a process gets handed back the CPU it prints a message
> again. Necessary?
Maybe not, but then again that should probably be taken up with the
Debian developers, not us.
> If necessary then at least a timestamp could be added to such lines.
> If the timestamp turns out to be the same, that means there is some
> bigger problem.
Are you suggesting that we should print a timestamp each time we start
and/or finish a compilation? I don't see that it would be very useful,
myself. The buffer you are looking at should only contain debugging
information, none of which is time sensitive.
So I don't think this is something that we want to do, and I'm closing
this bug report.
prev parent reply other threads:[~2022-11-25 0:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 7:00 bug#59269: Maybe add timestamps to *Async-native-compile-log* by default Dan Jacobson
2022-11-15 4:01 ` Stefan Kangas
2022-11-17 11:19 ` Dan Jacobson
2022-11-25 0:55 ` Stefan Kangas [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='CADwFkmmAbYi-zan0M=3us=FukZoswuoLeLvGVAw7oCie2eHmHw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=59269@debbugs.gnu.org \
--cc=jidanni@jidanni.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).