unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 12:07:31 -0700	[thread overview]
Message-ID: <AE7C3770E9BE422DA794D3EFF86DF47D@us.oracle.com> (raw)
In-Reply-To: <BANLkTinB9gcCZHwK0Hg1F=dkoMdJaS-JFw@mail.gmail.com>

> With lexical binding, (defvar foobar) is used to tell the bytecompiler
> that the variable has dynamic scope.

It's still a vacuous definition.  And any defvar tells the byte compiler that a
variable has dynamic scope, no?

This seems irrelevant to the bug report.  I'd still suggest removing vacuous
defvars from the menu.  Mixing in vacuous entries with entries that really
define variables distracts users.  You want to think that accessing a menu item
will take you to a real variable definition.

If someone wants to provide vacuous defvars in a different submenu from
`Variables' (e.g. `Vacuous Vars') I have no problem with that.  But I don't
really think that's needed.

FWIW, this is what I use in my code (imenu+.el):

(concat "^\\s-*("
        (regexp-opt
          '("defvar" "defconst" "defconstant" "defcustom"
            "defparameter" "define-symbol-macro") t)
        "\\s-+\\(\\sw\\(\\sw\\|\\s_\\)+\\)"
        "\\s-+[^) \t\n]")

Not perfect, perhaps, but it seems to do the job OK so far.






  reply	other threads:[~2011-05-08 19:07 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 [this message]
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
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=AE7C3770E9BE422DA794D3EFF86DF47D@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).