bug#59269: Maybe add timestamps to *Async-native-compile-log* by default

bug#59269: Maybe add timestamps to *Async-native-compile-log* by default

[Dan Jacobson]

We notice buffer
 %* *Async-native-compile-log* 96952 Fundamental
$ sort|uniq -c|sort -nr
gives:
    145 Loading debian-ispell...
    145 Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)...
    145 Loading /var/cache/dictionaries-common/emacsen-ispell-default.el (source)...
    145 Loading /etc/emacs/site-start.d/70x-face-el.el (source)...
    145 Loading /etc/emacs/site-start.d/50w3m-el-snapshot.el (source)...
    145 Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...
    145 Loading /etc/emacs/site-start.d/50dictem.el (source)...
    145 Loading /etc/emacs/site-start.d/50bbdb3.el (source)...
    145 Loading /etc/emacs/site-start.d/50autoconf.el (source)...
    145 Loading /etc/emacs/site-start.d/00debian.el (source)...
      8 Compilation finished.
      1 Compiling /usr/share/emacs/site-lisp/w3m/w3m.el...
      1 Compiling /usr/share/emacs/site-lisp/w3m/w3m-util.el...
OK, fine. But maybe add timestamps to the buffer by default.
GNU Emacs 28.2

bug#59269: Maybe add timestamps to *Async-native-compile-log* by default

[Stefan Kangas]

Dan Jacobson <jidanni@jidanni.org> writes:

> We notice buffer
>  %* *Async-native-compile-log* 96952 Fundamental
> $ sort|uniq -c|sort -nr
> gives:
>     145 Loading debian-ispell...
>     145 Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)...
>     145 Loading /var/cache/dictionaries-common/emacsen-ispell-default.el (source)...
>     145 Loading /etc/emacs/site-start.d/70x-face-el.el (source)...
>     145 Loading /etc/emacs/site-start.d/50w3m-el-snapshot.el (source)...
>     145 Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...
>     145 Loading /etc/emacs/site-start.d/50dictem.el (source)...
>     145 Loading /etc/emacs/site-start.d/50bbdb3.el (source)...
>     145 Loading /etc/emacs/site-start.d/50autoconf.el (source)...
>     145 Loading /etc/emacs/site-start.d/00debian.el (source)...
>       8 Compilation finished.
>       1 Compiling /usr/share/emacs/site-lisp/w3m/w3m.el...
>       1 Compiling /usr/share/emacs/site-lisp/w3m/w3m-util.el...
> OK, fine. But maybe add timestamps to the buffer by default.
> GNU Emacs 28.2

I don't think I understand what you are saying.

Could you please elaborate on what problem it is that you are seeing, or
what feature you are suggesting?

bug#59269: Maybe add timestamps to *Async-native-compile-log* by default

[Dan Jacobson]

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?
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.

bug#59269: Maybe add timestamps to *Async-native-compile-log* by default

[Stefan Kangas]

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.