public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Kacur <jkacur@rogers.com>
To: sam@ravnborg.org, kai.germaschewski@unh.edu
Cc: linux-kernel@vger.kernel.org
Subject: Exuberant ctags can tag files names too
Date: Wed, 09 Mar 2005 21:01:08 -0500	[thread overview]
Message-ID: <1110420068.5526.39.camel@linux.site> (raw)

Exuberant ctags can tag file names too. I find this extremely useful
when browsing kernel source, and so would like to share it with
everyone. (You can now type ":tag oprof.c" for example, and jump to the
file with that name.)

I previously sent a patch which naively just appended an "--extra=+f" to
the ctags line. Here's a much smarter patch that works by first
querrying if ctags is exuberant, and if so, whether the --extra
functionality is available before adding the line. Please apply.
Signed-off-by: John Kacur jkacur@rogers.com

--- Makefile.orig	2005-03-08 23:34:16.000000000 -0500
+++ Makefile	2005-03-09 20:25:06.710159432 -0500
@@ -1167,12 +1167,13 @@
 cmd_TAGS = $(all-sources) | etags -
 
 # 	Exuberant ctags works better with -I
-
+#	Exuberant ctags can tag file names with --extra=+f
 quiet_cmd_tags = MAKE   $@
 define cmd_tags
 	rm -f $@; \
-	CTAGSF=`ctags --version | grep -i exuberant >/dev/null && echo "-I
__initdata,__exitdata,EXPORT_SYMBOL,EXPORT_SYMBOL_GPL"`; \
-	$(all-sources) | xargs ctags $$CTAGSF -a
+	CTAGSF=`ctags --version | grep -iq exuberant && echo "-I
__initdata,__exitdata,EXPORT_SYMBOL,EXPORT_SYMBOL_GPL"`; \
+	CTAGSF_EXTRA=`ctags --version | grep -iq exuberant && ctags --help |
grep -q "\--extra" && echo "--extra=+f"`; \
+	$(all-sources) | xargs ctags $$CTAGSF -a $$CTAGSF_EXTRA
 endef
 
 TAGS: FORCE

This second patch is a trivial spelling correction. Please apply
Signed-off-by: John Kacur jkacur@rogers.com

--- Makefile.orig	2005-03-08 23:34:16.000000000 -0500
+++ Makefile	2005-03-09 20:26:29.063639800 -0500
@@ -18,7 +18,7 @@
 #
 # Most importantly: sub-Makefiles should only ever modify files in
 # their own directory. If in some directory we have a dependency on
-# a file in another dir (which doesn't happen often, but it's of
+# a file in another dir (which doesn't happen often, but it's often
 # unavoidable when linking the built-in.o targets which finally
 # turn into vmlinux), we will call a sub make in that other dir, and
 # after that we are sure that everything which is in that other dir


Kai, your e-mail address which I found in the list is different than the
one listed in the MAINTAINERS file.



             reply	other threads:[~2005-03-10  2:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10  2:01 John Kacur [this message]
2005-03-14 20:09 ` Exuberant ctags can tag files names too Sam Ravnborg
2005-03-14 20:44   ` Andreas Dilger

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=1110420068.5526.39.camel@linux.site \
    --to=jkacur@rogers.com \
    --cc=kai.germaschewski@unh.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox