all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 400@debbugs.gnu.org
Subject: bug#400: 23.0.60; C-h v should pick up lispified name in Customize
Date: Thu, 21 Oct 2021 12:45:15 -0700	[thread overview]
Message-ID: <CADwFkmm_xszvoR7kynSqQ6d6MQUTvhCe=6yRm4BpnmFgJkoQJg@mail.gmail.com> (raw)
In-Reply-To: <83ilxq8dhb.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 21 Oct 2021 21:00:32 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> No, you can customize it directly from `customize-group'.
>
> When you do, I'm okay with fully expanding the doc string of the
> variable which you are customizing from the groups buffer.  Would that
> solve the issue at hand?

I don't think I understand what this proposal means.  Could you perhaps
spell it out more explicitly?

>> But I'm not sure what you mean by "complicating commands" given that the
>> proposal AFAIU is to introduce a specific `customize-describe-variable'
>> bound to `C-h v' that handles also the unlispified names.
>
> How would you implement that without complicating the command?  The
> unlispified name is just several English words.

Maybe we are miscommunicating.  I mean that if we add a new command
`customize-describe-variable', it won't complicate `describe-variable'.

> Why do we need to make Emacs so much more complex for the benefit of
> an obscure use case, which already has more than one existing
> solution?

I just noticed that we already have such handling of unlispified names
in `C-h S', which is IMO a useful DWIM feature.  So this wouldn't be
that different.

>> I believe the activity we are engaged in right now is currently as good
>> as it gets.  FWIW, if I had my way, I would for sure close bugs and
>> feature requests far more enthusiastically than is being done now.
>
> Please do, then.  IMNSHO, a proposal for a minor feature that exists
> for more than a decade, and was discussed at length without generating
> any reasonable consensus, should be closed as wontfix.
>
>> For example, "wontfix" could also be used meaning: "yes, it's an issue
>> but it's not one we consider worth fixing, if you care enough send a
>> patch and we will reconsider".
>
> Exactly.

This message has been received; I'll try to apply it with the necessary
restraint.  I expect that you will let me know if I don't.  ;-)





  reply	other threads:[~2021-10-21 19:45 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 16:27 bug#400: 23.0.60; C-h v should pick up lispified name in Customize Drew Adams
2008-06-12 21:19 ` martin rudalics
2008-06-12 21:28   ` Drew Adams
2020-09-06 12:26 ` Lars Ingebrigtsen
2020-09-06 14:39   ` Eli Zaretskii
2020-09-06 16:33     ` Kévin Le Gouguec
2021-10-20 21:02     ` Stefan Kangas
2021-10-20 21:27       ` bug#400: [External] : " Drew Adams
2021-10-21  6:37         ` Eli Zaretskii
2021-10-21 16:15           ` Drew Adams
2021-10-21  3:09       ` Lars Ingebrigtsen
2021-10-21  3:35         ` Stefan Kangas
2021-10-21  3:38           ` Lars Ingebrigtsen
2021-10-21  5:01             ` bug#400: [External] : " Drew Adams
2021-10-21  7:40               ` Eli Zaretskii
2021-10-21 16:49             ` Stefan Kangas
2021-10-22 14:29               ` Lars Ingebrigtsen
2021-10-22 17:13                 ` bug#400: [External] : " Drew Adams
2021-10-21  4:26         ` Drew Adams
2021-10-21  7:36           ` Eli Zaretskii
2021-10-21  6:31       ` Eli Zaretskii
2021-10-21 15:47         ` Howard Melman
2021-10-21 17:02           ` Eli Zaretskii
2021-10-22  2:36             ` Howard Melman
2021-10-22  6:38               ` Eli Zaretskii
2021-10-22 15:38                 ` Howard Melman
2021-10-22 17:22                   ` bug#400: [External] : " Drew Adams
2021-10-21 16:34         ` Stefan Kangas
2021-10-21 17:09           ` Eli Zaretskii
2021-10-21 17:50             ` Stefan Kangas
2021-10-21 18:00               ` Eli Zaretskii
2021-10-21 19:45                 ` Stefan Kangas [this message]
2021-10-22  6:05                   ` Eli Zaretskii
2021-10-22  8:12                     ` Stefan Kangas
2021-10-22 10:49                       ` Eli Zaretskii
2021-10-22 16:56                     ` bug#400: [External] : " Drew Adams
2021-10-22  3:30           ` Howard Melman
2021-10-22 16:51             ` bug#400: [External] : " Drew Adams
2021-10-23 18:25               ` Juri Linkov
2020-09-06 17:06   ` Drew Adams
     [not found] <<007f01c8cca9$3cbbf770$c2b22382@us.oracle.com>
     [not found] ` <<875z8rum4k.fsf@gnus.org>
     [not found]   ` <<83o8mjnf5n.fsf@gnu.org>
2020-09-06 17:13     ` Drew Adams

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkmm_xszvoR7kynSqQ6d6MQUTvhCe=6yRm4BpnmFgJkoQJg@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=400@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.