From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.com>,
"'Ted Zlatanov'" <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: RE: Recent change to describe-variable
Date: Mon, 4 Apr 2011 06:03:09 -0700 [thread overview]
Message-ID: <77BECCED88B440C6A9F9C01692854B66@us.oracle.com> (raw)
In-Reply-To: <BANLkTikqj9iMr8HKO9N6ivz0Co+FOkxkTQ@mail.gmail.com>
> > 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
Oh, are we now installing things at the request of one Emacs user/developer?
Someone has an idea s?he thinks is good, so it's installed as part of Emacs?
> 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).
Keywords with a doc string and without. I agree with the post below by Stefan
to the cited thread: if it has a doc string, include it. And even if it doesn't
have a doc string, include it ("No documentation" is useful information.)
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.
It ain't broke. Please don't fix it. Let _users_ filter things as they like.
And if some user wants a specialized "`my-describe-emacs-variable' or
`my-describe-documented-variable' then s?he can define the command and post it
to the wiki. It's not rare (or difficult) for a user to define a specialized
`describe-*' command.
Emacs doesn't need it.
Especially as a replacement for `describe-variable'.
next prev parent reply other threads:[~2011-04-04 13:03 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 [this message]
2011-04-04 13:34 ` Ted Zlatanov
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
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=77BECCED88B440C6A9F9C01692854B66@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=tzz@lifelogs.com \
/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).