[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#44852: [PATCH] Fix modification check when custom-form is 'lisp
From: |
Dario Gjorgjevski |
Subject: |
bug#44852: [PATCH] Fix modification check when custom-form is 'lisp |
Date: |
Tue, 24 Nov 2020 19:51:38 +0100 |
When a variable’s custom-form is 'lisp (or 'mismatch),
`custom-variable-value-create' will quote its value prior to storing it
inside the widget. Afterwards, `custom-variable-modified-p' will try to
compare this quoted form to the (unquoted) value and think that the
variable has been modified.
To reproduce, fire up emacs -Q and do:
1. (setq custom-variable-default-form 'lisp)
2. M-x customize-variable RET auto-save-file-name-transforms RET
You will notice that Customize thinks that the variable has been
modified even though that is not true. If step 1. is omitted,
everything is fine.
The patch attached below fixes that.
0001-Fix-modification-check-when-custom-form-is-lisp.patch
Description: Fix modification check when custom-form is 'lisp
Best regards,
Dario
--
$ keyserver=hkps://hkps.pool.sks-keyservers.net
$ keyid=744A4F0B4F1C9371
$ gpg --keyserver $keyserver --search-keys $keyid
- bug#44852: [PATCH] Fix modification check when custom-form is 'lisp,
Dario Gjorgjevski <=