From: Eli Zaretskii <eliz@gnu.org>
To: Mauro Aranda <maurooaranda@gmail.com>,
Stefan Kangas <stefankangas@gmail.com>
Cc: ola.x.nilsson@axis.com, stephen.berman@gmx.net, 64046@debbugs.gnu.org
Subject: bug#64046: 30.0.50; Quoting in customize choice tags
Date: Thu, 31 Aug 2023 08:41:42 +0300 [thread overview]
Message-ID: <835y4vg44p.fsf@gnu.org> (raw)
In-Reply-To: <1886f854-101b-00ef-f619-28ac99082eb5@gmail.com> (message from Mauro Aranda on Wed, 30 Aug 2023 19:58:26 -0300)
> Cc: Ola x Nilsson <ola.x.nilsson@axis.com>, 64046@debbugs.gnu.org
> Date: Wed, 30 Aug 2023 19:58:26 -0300
> From: Mauro Aranda <maurooaranda@gmail.com>
>
> Stephen Berman <stephen.berman@gmx.net> writes:
>
> > On Wed, 30 Aug 2023 19:33:21 -0300 Mauro Aranda
> <maurooaranda@gmail.com> wrote:
> >
> >> Stephen Berman <stephen.berman@gmx.net> writes:
> >>
> >>> On Wed, 30 Aug 2023 12:29:47 -0300 Mauro Aranda
> <maurooaranda@gmail.com>
> >> wrote:
> >>>
> >>>> Stephen Berman <stephen.berman@gmx.net> writes:
> >>>>
> >>>>> On Mon, 28 Aug 2023 11:33:09 +0200 Ola x Nilsson
> <ola.x.nilsson@axis.com>
> >>>> wrote:
> >>>>>
> >>>>>> I agree that quote substition should be done on the car of
> simple item
> >>>>>> definitions. I have no opinion on susbstitute-command-keys vs
> >>>>>> substitute-quotes. But I came to think about the TITLE argument,
> >>>>>> shouldn't quote substition be performed on it as well?
> >>>>>
> >>>>> I think you're right about that as well, since the title is simply a
> >>>>> display feature. AFAIK it wouldn't make a noticeable difference for
> >>>>> existing uses of widget-choose in the Customize UI (in the Value menu
> >>>>> the title is simply "Choice" and in the State menu it's "Operation on
> >>>>> <option name>"), but it might be relevant for third party uses or
> future
> >>>>> uses in Emacs, as well as for ad-hoc uses of simple item definitions.
> >>>>> So applying substition to all uses of TITLE seems appropriate. The
> >>>>> below patch does this, and also corrects my previous patch by
> excluding
> >>>>> substition from the cdr of simple item definitions.
> >>>>
> >>>> What would be a real-life scenario where we need to use
> >>>> substitute-command-keys on TITLE? I can't think of any.
> >>>
> >>> I can't think of a really convincing example where it's needed, but
> just
> >>> as a possibility for stylistic variation, e.g. for simple item
> >>> definitions one could have a more explicit prompt like this:
> >>>
> >>> (widget-choose "Type `0' or `1'" '(("Use `a'" . "Use `1'") ("Use `b'"
> >>> . "Use `2'")))
> >>>
> >>> which would appear as "Type ‘0’ or ‘1’" with curve-style quotes. For
> >>> the Customize UI, although the title is currently hard-coded as
> >>> "Choice", one could define a widget with a title like "User's choice",
> >>> which would appear as "User’s choice" with the curve-style quote.
> >>> Unless some undesirable consequence of applying substitute-command-keys
> >>> to TITLE is found, I don't see any harm in allowing such uses.
> >>
> >> I vote for don't adding code until it's really needed, and since there
> >> isn't a real feature request for that, I'd leave it out.
> >
> > Well, I took Ola Nilsson's post which drew attention to the possibility
> > of applying quote substition to TITLE (quoted above), as an implicit
> > feature request, and found it plausible. But...
> >
> >> Looks like we
> >> disagree on this, and it's not really my call, so let's leave it for a
> >> maintainer to decide whether to add that line of code or not.
> >
> > ... I don't have any problem leaving TITLE alone for now. And I do
> > agree with you that an Emacs maintainer should make the decision (also
> > about whether to retain substitute-command-keys or instead use
> > substitute-quotes).
>
> Let's wait then. And thank you for taking the time to write the code
> for it.
Stefan, any comments on this issue?
next prev parent reply other threads:[~2023-08-31 5:41 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 14:02 bug#64046: 30.0.50; Quoting in customize choice tags Stephen Berman
2023-06-13 15:56 ` Eli Zaretskii
2023-06-14 19:51 ` Mauro Aranda
2023-06-14 20:05 ` Mauro Aranda
2023-06-15 11:39 ` Stephen Berman
2023-06-22 20:07 ` Stephen Berman
2023-06-22 22:59 ` Mauro Aranda
2023-06-23 22:18 ` Stephen Berman
2023-06-24 6:37 ` Eli Zaretskii
2023-06-24 8:50 ` Stephen Berman
2023-07-15 13:20 ` Mauro Aranda
2023-07-20 15:48 ` Stephen Berman
2023-07-20 19:11 ` Mauro Aranda
2023-07-20 19:53 ` Stephen Berman
2023-08-21 12:04 ` Ola x Nilsson
2023-08-21 14:51 ` Mauro Aranda
2023-08-24 12:51 ` Stephen Berman
2023-08-24 13:19 ` Stephen Berman
2023-08-24 20:14 ` Mauro Aranda
2023-08-24 20:54 ` Stephen Berman
2023-08-24 21:58 ` Mauro Aranda
2023-08-25 8:02 ` Ola x Nilsson
2023-08-25 21:50 ` Stephen Berman
2023-08-28 9:33 ` Ola x Nilsson
2023-08-28 13:50 ` Stephen Berman
2023-08-30 15:29 ` Mauro Aranda
2023-08-30 16:29 ` Stephen Berman
2023-08-30 22:33 ` Mauro Aranda
2023-08-30 22:51 ` Stephen Berman
2023-08-30 22:58 ` Mauro Aranda
2023-08-31 5:41 ` Eli Zaretskii [this message]
2023-08-31 6:43 ` Stefan Kangas
2023-08-31 15:43 ` Drew Adams
2023-08-31 20:52 ` Stefan Kangas
2023-08-31 22:10 ` Drew Adams
2023-08-31 22:59 ` Stefan Kangas
2023-09-01 1:08 ` Drew Adams
2023-09-01 6:34 ` Eli Zaretskii
2023-09-01 16:17 ` Drew Adams
2023-09-01 23:29 ` Stephen Berman
2023-09-01 23:38 ` Stefan Kangas
2023-09-02 9:49 ` Stephen Berman
2023-09-02 18:59 ` Stefan Kangas
2023-09-02 21:25 ` Stephen Berman
2023-09-02 2:12 ` Drew Adams
2023-09-01 6:16 ` Eli Zaretskii
2023-09-01 16:32 ` Drew Adams
2023-08-24 20:53 ` Stefan Kangas
2023-08-24 21:10 ` Stephen Berman
2023-08-24 21:14 ` Stefan Kangas
2023-08-24 21:41 ` Stephen Berman
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=835y4vg44p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64046@debbugs.gnu.org \
--cc=maurooaranda@gmail.com \
--cc=ola.x.nilsson@axis.com \
--cc=stefankangas@gmail.com \
--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).