From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Help etags parse lisp.j
Date: Mon, 21 Mar 2016 14:28:59 -0700 [thread overview]
Message-ID: <m2io0fr04k.fsf@newartisans.com> (raw)
In-Reply-To: <83mvpr66nf.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 21 Mar 2016 20:13:40 +0200")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> I don't want to turn it off, sorry. Etags is part of the set of tools that
> are invaluable when you are assigned with a task of making some change in a
> large project that lay dormant for years -- they allow you to quickly find
> your way in unfamiliar code. It should support old code styles.
Eli is very right on this point. Often, when Etags helps best is when you know
the least about the code being examined.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-03-21 21:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 17:19 Help etags parse lisp.j Eli Zaretskii
2016-03-20 17:34 ` Andreas Schwab
2016-03-20 17:59 ` Eli Zaretskii
2016-03-20 18:11 ` Help etags parse lisp.h Eli Zaretskii
2016-03-21 7:54 ` Help etags parse lisp.j Paul Eggert
2016-03-21 10:58 ` Andreas Schwab
2016-03-21 16:10 ` Eli Zaretskii
2016-03-22 12:46 ` Stefan Monnier
2016-03-22 16:24 ` Eli Zaretskii
2016-03-21 13:40 ` Stefan Monnier
2016-03-21 16:22 ` Eli Zaretskii
2016-03-21 17:40 ` Paul Eggert
2016-03-21 18:13 ` Eli Zaretskii
2016-03-21 21:28 ` John Wiegley [this message]
2016-03-22 12:25 ` Stefan Monnier
2016-03-21 18:10 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2io0fr04k.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.