From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 8638@debbugs.gnu.org
Subject: bug#8638: 24.0.50; Imenu should not include vacuous defvars
Date: Sun, 8 May 2011 22:29:32 +0200 [thread overview]
Message-ID: <BANLkTin-R=7=ph2YdY+hwqWq-fjnutX5Ww@mail.gmail.com> (raw)
In-Reply-To: <567CCE5B717E445496B4F685457F16AB@us.oracle.com>
On Sun, May 8, 2011 at 22:03, Drew Adams <drew.adams@oracle.com> wrote:
> When you follow a Variables menu entry to its code, you want to see what the
> code for the variable is. You do not want to see only a vacuous defvar that
> provides no more information than the menu item itself.
The imenu index is not documentation. It is an index to code. So if
the "vacuous variable" has twenty lines of comment explaining its
purpose and why it does not have or require a docstring or an initial
value, I fully expect imenu to help me get there too, just as if it
were a normal, "full" variable. Your expectations for imenu are just
that, your expectations. I prefer to be the judge of what it is
interesting in the code and what is not, not some imenu filter.
But that's just my opinion. I'm not going to complain if someone fixes
this bug to your liking.
Juanma
next prev parent reply other threads:[~2011-05-08 20:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 18:15 bug#8638: 24.0.50; Imenu should not include vacuous defvars Drew Adams
2011-05-08 18:50 ` Juanma Barranquero
2011-05-08 19:07 ` Drew Adams
2011-05-08 19:25 ` Juanma Barranquero
2011-05-08 19:36 ` Drew Adams
2011-05-08 19:46 ` Juanma Barranquero
2011-05-08 19:46 ` Juanma Barranquero
2011-05-08 20:03 ` Drew Adams
2011-05-08 20:29 ` Juanma Barranquero [this message]
2011-05-08 20:39 ` Drew Adams
2011-05-08 20:52 ` Juanma Barranquero
2011-05-08 21:49 ` Drew Adams
2011-05-27 16:00 ` Drew Adams
2012-08-05 14:15 ` Chong Yidong
2012-08-05 16:27 ` Drew Adams
2012-08-06 3:43 ` Chong Yidong
2012-08-06 3:52 ` Drew Adams
2011-05-09 14:19 ` Stefan Monnier
2011-05-09 14:31 ` 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='BANLkTin-R=7=ph2YdY+hwqWq-fjnutX5Ww@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=8638@debbugs.gnu.org \
--cc=drew.adams@oracle.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).