unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Laurence Warne <laurencewarne@gmail.com>
Cc: mattiase@acm.org, 73441@debbugs.gnu.org, Sam James <sam@gentoo.org>
Subject: bug#73441: 31.0.50; Unstable proced-refine-test failure
Date: Wed, 13 Nov 2024 09:04:04 +0100	[thread overview]
Message-ID: <87zfm3lfuz.fsf@gmx.de> (raw)
In-Reply-To: <CAE2oLqhpOocxLQaavUGQ2=PqzZEpo=0v58utS9f6d_iTJ8u+-w@mail.gmail.com> (Laurence Warne's message of "Tue, 12 Nov 2024 20:19:42 +0000")

Laurence Warne <laurencewarne@gmail.com> writes:

> Hi Michael,

Ni Laurence,

> I added a conditional skip for the refine tests if it looks like
> there's a NaN, let me know if it looks ok.

Thanks. In general it looks fine, but I have one nit: In
proced--assert-process-valid-cpu-refinement-explainer you still call
(thing-at-point 'number). But the explainer is active in case of
problems, so it is likely that there isn't a number. Wouldn't it be
better to call (thing-at-point 'symbol)? Or something like
(or (thing-at-point 'number) (thing-at-point 'sexp))?

> Thanks, Laurence

Best regards, Michael.





  reply	other threads:[~2024-11-13  8:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23 13:19 bug#73441: 31.0.50; Unstable proced-refine-test failure Sam James
2024-09-27 13:00 ` Laurence Warne
2024-10-15 14:52   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-25 16:46     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-26 15:44       ` Laurence Warne
2024-10-26 16:59         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 11:16           ` Laurence Warne
2024-10-27 11:47             ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 12:07               ` Eli Zaretskii
2024-10-27 15:53                 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-29  7:51         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-29 21:26           ` Laurence Warne
2024-10-30 14:15             ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-30 18:25               ` Laurence Warne
2024-11-04 13:27                 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-09  8:31                   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-09 14:17                     ` Laurence Warne
2024-11-09 20:06                       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-09 21:18                         ` Laurence Warne
2024-11-10  8:35                           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-12 20:19                             ` Laurence Warne
2024-11-13  8:04                               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-11-14 18:24                                 ` Laurence Warne
2024-11-15 15:25                                   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87zfm3lfuz.fsf@gmx.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=73441@debbugs.gnu.org \
    --cc=laurencewarne@gmail.com \
    --cc=mattiase@acm.org \
    --cc=michael.albinus@gmx.de \
    --cc=sam@gentoo.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).