GNU bug report logs - #73084
[PATCH] Include the variable name in the `setopt` warning

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Okamsn <okamsn <at> protonmail.com>
Subject: bug#73084: closed (Re: bug#73084: [PATCH] Include the variable
 name in the `setopt` warning)
Date: Sun, 08 Sep 2024 06:23:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#73084: [PATCH] Include the variable name in the `setopt` warning

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 73084 <at> debbugs.gnu.org.

-- 
73084: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=73084
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Okamsn <okamsn <at> protonmail.com>
Cc: 73084-done <at> debbugs.gnu.org
Subject: Re: bug#73084: [PATCH] Include the variable name in the `setopt`
 warning
Date: Sun, 08 Sep 2024 09:21:59 +0300

> Date: Sat, 07 Sep 2024 00:23:00 +0000
> From:  Okamsn via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
> 
> The attached patch adds the variable name to the `setopt` warning.
> 
> I write my Emacs config in an Org file, from which I make the Emacs Lisp 
> file.  Currently, if `setopt` detects that the value I wish to make a 
> variable hold does not conform to the variable's Custom.el type, then it 
> reports the type and the problematic value, but not the variable itself, 
> when I open Emacs.  This adds extra steps to editing the code in the Org 
> file to fix the warning, especially when the value is created 
> programmatically.  It would be faster to search for the variable name 
> directly in the Org file and to then re-tangle the Org file.

Thanks, I made the warning say

  Value `foo' for variable `bar' does not match its type "type"

I installed this on the master branch, and I'm therefore closing this
bug.

[Message part 3 (message/rfc822, inline)]

From: Okamsn <okamsn <at> protonmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: [PATCH] Include the variable name in the `setopt` warning
Date: Sat, 07 Sep 2024 00:23:00 +0000

[Message part 4 (text/plain, inline)]

Hello,

The attached patch adds the variable name to the `setopt` warning.

I write my Emacs config in an Org file, from which I make the Emacs Lisp 
file.  Currently, if `setopt` detects that the value I wish to make a 
variable hold does not conform to the variable's Custom.el type, then it 
reports the type and the problematic value, but not the variable itself, 
when I open Emacs.  This adds extra steps to editing the code in the Org 
file to fix the warning, especially when the value is created 
programmatically.  It would be faster to search for the variable name 
directly in the Org file and to then re-tangle the Org file.

Thank you.

[0001-Include-the-variable-name-in-the-warning-in-setopt-s.patch (text/x-patch, attachment)]

Previous Next

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