all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Recent change to describe-variable
Date: Mon, 04 Apr 2011 08:34:03 -0500	[thread overview]
Message-ID: <87d3l2cf90.fsf@lifelogs.com> (raw)
In-Reply-To: 77BECCED88B440C6A9F9C01692854B66@us.oracle.com

On Mon, 4 Apr 2011 06:03:09 -0700 "Drew Adams" <drew.adams@oracle.com> wrote: 

>> > So if `C-h v' AKA `describe-variable' is going to describe 
>> > everything, it should at least filter out self-quoting :symbols
>> 
>> At your request I installed a change to exclude :keywords

DA> Oh, are we now installing things at the request of one Emacs
DA> user/developer?  Someone has an idea s?he thinks is good, so it's
DA> installed as part of Emacs?

Yes, I believe that's exactly how it works.  I don't know why you're
acting surprised.

>> but the lexbind-new merge overrode it. So if the current
>> predicate is removed it would be good to filter out keywords
>> again (though it makes sense to let pass keywords with a
>> docstring, which my original patch didn't).

DA> Keywords with a doc string and without.  I agree with the post below by Stefan
DA> to the cited thread: if it has a doc string, include it.  And even if it doesn't
DA> have a doc string, include it ("No documentation" is useful information.)

I was specifically talking about self-quoting symbols.  Putting them in
`describe-variable' is like putting personal names like "John" and
"Nick" in the dictionary.  Besides being incorrect, there are proper
nouns and verbs like "john" and "nick."

j> (defconst :mykeyword :mykeyword)
j> and even if you add a docstring to that, I'm not sure it is sensible
j> to show it as a completion of describe-variable...
s> 
s> Actually, if it has a docstring, it definitely makes sense.  And if it
s> doesn't, then it's not that much of a problem to include those rare
s> cases in the completion.

DA> Let _users_ filter things as they like.  And if some user wants a
DA> specialized "`my-describe-emacs-variable' or
DA> `my-describe-documented-variable' then s?he can define the command
DA> and post it to the wiki.  It's not rare (or difficult) for a user to
DA> define a specialized `describe-*' command.

But that's ridiculous, shifting the burden to the user.  `C-h v' is a
first-class command; it's very visible and very important.  It should
not offer garbage.  How could it possibly benefit the user to offer
undocumented self-quoting symbols for completion to `describe-variable'?

Ted




  reply	other threads:[~2011-04-04 13:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03  0:15 Recent change to describe-variable Chong Yidong
2011-04-03  0:33 ` Drew Adams
2011-04-04  9:41 ` Ted Zlatanov
2011-04-04 10:23   ` Juanma Barranquero
2011-04-04 10:41     ` Ted Zlatanov
2011-04-04 13:03     ` Drew Adams
2011-04-04 13:34       ` Ted Zlatanov [this message]
2011-04-04 14:46       ` Juanma Barranquero
2011-04-04 16:08     ` Chong Yidong
2011-04-04 16:11       ` Juanma Barranquero
2011-04-04 13:46 ` Stefan Monnier
2011-04-04 17:05   ` Chong Yidong
2011-04-04 21:47     ` Stefan Monnier
2011-04-04 22:09       ` Juanma Barranquero
2011-04-04 22:24         ` Juanma Barranquero

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=87d3l2cf90.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@gnu.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.