From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.com>
Cc: 8638@debbugs.gnu.org
Subject: bug#8638: 24.0.50; Imenu should not include vacuous defvars
Date: Sun, 8 May 2011 14:49:04 -0700 [thread overview]
Message-ID: <3361268F57984EC8826DCC27DE425C7D@us.oracle.com> (raw)
In-Reply-To: <BANLkTi=hhM4V85Mp3PHLqXTjwk4osWaUfA@mail.gmail.com>
> > it is a judgment call based on expectations of what most
> > users will want/expect.
>
> Not users. Developers. And developers are usually interested in a
> package's variables. More so in a lexical-binding context, where the
> fact that the defvar exists can (and does) alter semantics.
Users includes users who develop, and more. Imenu is for all Emacs users,
including developers. And the question is not whether developers are interested
in a package's variables. It is whether the Variables submenu should include
entries for vacuous defvars.
next prev parent reply other threads:[~2011-05-08 21:49 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
2011-05-08 20:39 ` Drew Adams
2011-05-08 20:52 ` Juanma Barranquero
2011-05-08 21:49 ` Drew Adams [this message]
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=3361268F57984EC8826DCC27DE425C7D@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=8638@debbugs.gnu.org \
--cc=lekktu@gmail.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).