GNU bug report logs - #64543
[PATCH] package-report-bug: don't fail on custom groups defined by eval

Previous Next

Full log

Message #38 received at 64543 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Spencer Baugh <sbaugh <at> catern.com>
Cc: sbaugh <at> janestreet.com, philipk <at> posteo.net, 64543 <at> debbugs.gnu.org
Subject: Re: bug#64543: [PATCH] package-report-bug: don't fail on custom
 groups defined by eval
Date: Sat, 15 Jul 2023 12:23:21 +0300

> Date: Sat, 15 Jul 2023 09:12:48 +0000 (UTC)
> From: Spencer Baugh <sbaugh <at> catern.com>
> Cc: Philip Kaludercic <philipk <at> posteo.net>, sbaugh <at> janestreet.com,
> 	64543 <at> debbugs.gnu.org
> 
> On Jul 15, 2023 04:57, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
>  >   >> Previously we just assumed that the car of an element of 
>  >   >> custom-current-group-alist was a filename.  But actually it can be nil 
>  >   >> if a custom group was defined by just evaling Lisp. 
>  >   > 
>  >   > Where is this behaviour documented?  I couldn't reproduce it with a 
>  >   > simple experiment. 
>  > 
>  >   To reproduce: 
>  >   M-: (defgroup mygroup nil "my group") RET 
>  > 
>  > The patch would ensure that if groups like these are defined (which 
>  > might happen by mistake), then `package-report-bug' will remain robust 
>  > and not fail due to a unrelated issue. 
> 
>  Is this case important enough to make this change so late in the 
>  pretest?  Spencer, how did you bump into this situation in Real Life?
> 
> I evaled a buffer containing a defgroup with C-c C-e (or maybe just a region?)

Why did you do that?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.