From: Mauro Aranda <maurooaranda@gmail.com>
To: Christopher League <league@contrapunctus.net>
Cc: 49274@debbugs.gnu.org
Subject: bug#49274: [PATCH] lisp/cus-theme: retain documentation string when customizing theme
Date: Tue, 29 Jun 2021 19:38:05 -0300 [thread overview]
Message-ID: <87im1wi9f6.fsf@tbb.theblackbeard.org> (raw)
In-Reply-To: <20210629144412.455196-1-league@contrapunctus.net> (Christopher League's message of "Tue, 29 Jun 2021 10:44:12 -0400")
Hello Christopher,
Christopher League <league@contrapunctus.net> writes:
> When editing an existing theme using `custom-theme-visit-theme`, the
> theme's documentation string would always be discarded and replaced
> with "Created DATE."
>
> With this improvement, the existing theme documentation string (if
> available) will be presented and editable in the widget, and emitted
> in the `deftheme` declaration when saved. A newly-created theme or an
> existing theme with no documentation string will get the "Created
> DATE" as before.
I think this is a good change.
> *Implementation details:* we had to move the chunk marked "Load the
> theme settings" earlier in the function `customize-create-theme`. Then
> the `custom-theme-description` widget was made an `editable-field`
> whose value comes from `theme-documentation` if available, else
> `format-time-string`. The rest of the patch is reindentation due to
> the larger scope of the let that holds the theme settings.
Why change the widget from a text widget to an editable-field
widget? I think a text widget is better here, since a docstring usually
would have more than one line, and the editable-field keymap remaps RET
while the text keymap doesn't.
next prev parent reply other threads:[~2021-06-29 22:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 14:44 bug#49274: [PATCH] lisp/cus-theme: retain documentation string when customizing theme Christopher League
2021-06-29 22:38 ` Mauro Aranda [this message]
2021-06-29 23:54 ` Christopher League
2021-06-30 0:03 ` Mauro Aranda
2021-06-30 1:57 ` Christopher League
2021-06-30 14:09 ` Mauro Aranda
2021-06-30 15:05 ` Christopher League
2021-07-03 13:23 ` Mauro Aranda
2021-07-03 13:30 ` Lars Ingebrigtsen
2021-07-03 13:52 ` Mauro Aranda
2021-07-03 13:35 ` Eli Zaretskii
2021-07-03 13:55 ` Mauro Aranda
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=87im1wi9f6.fsf@tbb.theblackbeard.org \
--to=maurooaranda@gmail.com \
--cc=49274@debbugs.gnu.org \
--cc=league@contrapunctus.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).