From: "D. Goel" <deego@glue.umd.edu>
Cc: Miles Bader <miles@gnu.org>, emacs-devel@gnu.org
Subject: Re: defvar vs setqif..
Date: 20 May 2002 15:40:18 -0400 [thread overview]
Message-ID: <ap3elg6d2vx.fsf@poynting.umd.edu> (raw)
In-Reply-To: <200205201924.g4KJOLh29045@rum.cs.yale.edu>
>
> There should be only one (defvar <var> <val>) form per variable.
> All others should only be (defvar <var>).
this resolves it for me.. i've been overlooking this... i guess i now
see what all of you have been trying to tell me. sorry to have wasted
all of your times...And indeed, as Miles was saying, the tag-finding
functions would/should know this rule...
re: actual concrete examples, indeed i have no examples when my TAGS
has ended up getting double-tags for a variable where the 2 tags come
from 2 libraries.. i guess this must be due to the reason you
mentioned above.... neither has my TAGS ever created a tag for a
defvar in my my .emacs even though my set-tags probes my .emacs and my
.emacs does have defvar's.. this must all be because the 'offending'
defvar's must be following the syntax you mention above.. So i humbly
withdraw my suggestion..
(there is one minor duplication---my TAGS seems to probe the
loaddefs-my.el too and creates 2 tag-entries for each autoloaded
defun/defvar---one where it was defined, and one for
loaddefs-my.el.. but that is quite unrelated to the present issue.. i
should simply request tags.el to overlook loaddefs-my.el when creating
TAGS, i guess..)..
Have a good day,
D <http://www.glue.umd.edu/~deego/>
--
next prev parent reply other threads:[~2002-05-20 19:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-19 20:44 defvar vs setqif D. Goel
2002-05-19 20:59 ` Colin Walters
2002-05-20 0:05 ` Miles Bader
2002-05-20 19:08 ` D. Goel
2002-05-20 19:41 ` Thien-Thi Nguyen
2002-05-20 19:47 ` Stefan Monnier
2002-05-21 13:13 ` D. Goel
2002-05-20 20:05 ` Kai Großjohann
2002-05-20 21:33 ` Richard Stallman
2002-05-20 0:03 ` Miles Bader
2002-05-20 19:00 ` D. Goel
2002-05-20 19:24 ` Stefan Monnier
2002-05-20 19:40 ` D. Goel [this message]
2002-05-20 23:15 ` Miles Bader
2002-05-21 13:18 ` D. Goel
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=ap3elg6d2vx.fsf@poynting.umd.edu \
--to=deego@glue.umd.edu \
--cc=emacs-devel@gnu.org \
--cc=miles@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 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).