From: Mauro Aranda <maurooaranda@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stephen.berman@gmx.net, 64347@debbugs.gnu.org
Subject: bug#64347: 30.0.50; Some customize faces shown as edited with -Q
Date: Mon, 10 Jul 2023 10:45:38 -0300 [thread overview]
Message-ID: <f6d1a54c-7984-098a-d704-ded9f5931f86@gmail.com> (raw)
In-Reply-To: <83sf9w7x1i.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sun, 9 Jul 2023 20:12:38 -0300
>> Cc: 64347@debbugs.gnu.org, stephen.berman@gmx.net
>> From: Mauro Aranda <maurooaranda@gmail.com>
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > OK, but why does it have to do that on the original value? It could
>> > do that on a copy that serves for the display and editing, in which
>> > case the original value could be left intact if the user didn't
change
>> > it or did change, but didn't click Apply. (If the user does modify
>> > the original value, then any conversions are okay, since the variable
>> > is really "edited".)
>>
>> I think my description was inaccurate, because it seemed to imply that
>> it is a destructive operation. It is not, it leaves the original value
>> intact.
>>
>> But when deciding to set a state, Custom always consults the spec built
>> from the data the face Widget has.
>
> Can we change this last aspect, so that the state is set using the
> original spec if the setting was not changed by the user?
That might be possible. I will check if it doesn't lead to any troubles
and if it actually fixes these inconsistencies.
next prev parent reply other threads:[~2023-07-10 13:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 10:15 bug#64347: 30.0.50; Some customize faces shown as edited with -Q Stephen Berman
2023-06-29 12:38 ` Eli Zaretskii
2023-06-30 11:33 ` Mauro Aranda
2023-06-30 12:43 ` Drew Adams
2023-06-30 14:05 ` Mauro Aranda
2023-07-08 7:49 ` Eli Zaretskii
2023-07-08 21:32 ` Mauro Aranda
2023-07-09 5:43 ` Eli Zaretskii
2023-07-09 11:44 ` Mauro Aranda
2023-07-09 12:13 ` Eli Zaretskii
2023-07-09 23:12 ` Mauro Aranda
2023-07-10 12:47 ` Eli Zaretskii
2023-07-10 13:45 ` Mauro Aranda [this message]
2023-07-15 20:01 ` Mauro Aranda
2023-07-20 15:45 ` Eli Zaretskii
2023-07-15 20:11 ` Mauro Aranda
2023-07-20 15:49 ` Eli Zaretskii
2023-07-20 18:56 ` Mauro Aranda
2023-07-20 19:09 ` Eli Zaretskii
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=f6d1a54c-7984-098a-d704-ded9f5931f86@gmail.com \
--to=maurooaranda@gmail.com \
--cc=64347@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stephen.berman@gmx.net \
/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).