all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, stefan@marxist.se, 400@debbugs.gnu.org
Subject: bug#400: [External] : Re: bug#400: 23.0.60; C-h v should pick up lispified name in Customize
Date: Thu, 21 Oct 2021 10:36:55 +0300	[thread overview]
Message-ID: <837de6akx4.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB548806B073A6597CE1D7257EF3BF9@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Thu, 21 Oct 2021 04:26:19 +0000)

> From: Drew Adams <drew.adams@oracle.com>
> CC: Eli Zaretskii <eliz@gnu.org>, "400@debbugs.gnu.org" <400@debbugs.gnu.org>
> Date: Thu, 21 Oct 2021 04:26:19 +0000
> Accept-Language: en-US
> 
> > What about making the unlispified variable name into a button?  It
> > could offer to take you to *Help* or to *info*, for instance.
> 
> Please read what I wrote about that today.

Please assume that everyone does read and take note of what you wrote,
and try not to reiterate that time and again, because doing so just
increases the noise level without adding anything useful.

> The Lisp name should appear (always), whether
> the phony, non-Lisp "name" appears or not, and
> whether or not the name is a link ("button")
> to the real *Help*.

Yes, you already said that.

> Emacs should be leading users, including those
> new to Lisp, toward Lisp, not away from it.
> And this is especially the case when it comes
> to knowledge about a user option.  There's no
> reason to hide the name of an option - quite
> the contrary.

Yes, you already said that.





  reply	other threads:[~2021-10-21  7:36 UTC|newest]

Thread overview: 40+ 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 [this message]
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
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

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=837de6akx4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=400@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.org \
    --cc=stefan@marxist.se \
    /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.