From: Doug Lewan <dougl@shubertticketing.com>
To: Doug Lewan <dougl@shubertticketing.com>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
Tom Roche <Tom_Roche@pobox.com>
Subject: RE: browser for bash scripts?
Date: Mon, 3 Dec 2012 14:43:07 +0000 [thread overview]
Message-ID: <155DEC68569B714B86C2C7075F5EDA9828D5F42F@DAKIYA1.pegasus.local> (raw)
In-Reply-To: <155DEC68569B714B86C2C7075F5EDA9828D5E3DB@DAKIYA1.pegasus.local>
Ignore my last comment. It turns out Exuberant ctags supports shell directly (and I assume it's better than my code). The problem for me (besides my own ignorance) had been that I wasn't using an extension to indicate the language.
Simply the following should work.
etags --language-force=sh files...
,Doug
> -----Original Message-----
> From: help-gnu-emacs-bounces+dougl=shubertticketing.com@gnu.org
> [mailto:help-gnu-emacs-bounces+dougl=shubertticketing.com@gnu.org] On
> Behalf Of Doug Lewan
> Sent: Monday, 2012 December 03 09:26
> To: help-gnu-emacs@gnu.org; Tom Roche
> Subject: RE: browser for bash scripts?
>
> I use exuberant ctags. (CYGWIN delivers it. You can also get it here:
> http://ctags.sourceforge.net/.)
>
> The following lines let me find shell functions as tags.
>
> etags --langdef=shell --regex-shell='/function
> [_[:alnum:]]+/[_[:alnum:]]+/' --language-force=shell files
> # etags might pick up tag-like things in comments. Get rid of
> them.
> sed -n -e '/#/d' -ep < TAGS > TTT && mv TTT TAGS
>
> It has changed my life. (Perhaps I need a better life....)
>
> ,Doug
>
> > -----Original Message-----
> > From: help-gnu-emacs-bounces+dougl=shubertticketing.com@gnu.org
> > [mailto:help-gnu-emacs-bounces+dougl=shubertticketing.com@gnu.org] On
> > Behalf Of Tom Roche
> > Sent: Sunday, 2012 June 03 23:07
> > To: help-gnu-emacs@gnu.org
> > Subject: browser for bash scripts?
> >
> >
> > Does anyone have code to make speedbar, ECB, or other code browser
> > display/navigate bash scripts? I'd like, e.g., to easily navigate
> > between variable and function definitions and calls/uses. Currently,
> > for the latter, I'm `find-grep`ing '^function ': that works, but is
> > not nearly so pleasant as was speedbar in JDEE (back when I did
> mostly
> > java, several years ago).
> >
> > TIA, Tom Roche <Tom_Roche@pobox.com>
>
prev parent reply other threads:[~2012-12-03 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 3:07 browser for bash scripts? Tom Roche
2012-11-29 6:26 ` Easior
[not found] ` <mailman.14117.1354247749.855.help-gnu-emacs@gnu.org>
2012-11-30 17:47 ` Stefan Monnier
2012-11-30 23:02 ` Thorsten Bonow
2012-12-01 11:28 ` Oleksandr Gavenko
2012-12-03 14:26 ` Doug Lewan
2012-12-03 14:43 ` Doug Lewan [this message]
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=155DEC68569B714B86C2C7075F5EDA9828D5F42F@DAKIYA1.pegasus.local \
--to=dougl@shubertticketing.com \
--cc=Tom_Roche@pobox.com \
--cc=help-gnu-emacs@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.
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).