From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Managing lots of source files (e.g. subroutines and functions)
Date: Tue, 27 Jan 2009 16:05:23 +0100 [thread overview]
Message-ID: <87wscgpz64.fsf@tux.homenetwork> (raw)
In-Reply-To: 7cocxtkqy0.fsf@pbourguignon.anevia.com
pjb@informatimago.com (Pascal J. Bourguignon) writes:
> Sebastian Schubert <schubert.seb@googlemail.com> writes:
>
>> Hi,
>>
>> I recently started to work an large project which is written in
>> Fortran90. It includes a lot of different source files included in just
>> one folder. Is there a way to make emacs scan this folder and create
>> some kind of procedure or subroutine or function list? I would like to
>> be able to directly move to the file where e.g. the function I'm
>> interested in is written.
>>
>> In addition a list of variables would be nice too.
>>
>> Any idea?
>
>
>
> The basic feature can be provided by etag(1)
>
> First, you build a TAGS file:
>
> find $source_directory -name \*.f -print0 | xargs -0 etags -a -o $source_directory/TAGS {}
NOTE:
If you use traverslisp.el, you can build a TAGS file easily from the
root of project with `traverse-build-tags-in-project'
> then you can use it for example, by typing M-. on a function name.
> The first time it'll ask what TAGS file you want (specify the one you
> just created). Then it will jump to the source of the function.
>
>
>
> Otherwise, you could use cedet (http://cedet.sourceforge.net) but it
> seems there's no Fortran parser yet. You could write one.
--
A + Thierry Volpiatto
Location: Saint-Cyr-Sur-Mer - France
prev parent reply other threads:[~2009-01-27 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 9:01 Managing lots of source files (e.g. subroutines and functions) Sebastian Schubert
2009-01-27 10:01 ` Pascal J. Bourguignon
2009-01-27 10:17 ` Sebastian Schubert
2009-01-27 15:05 ` Thierry Volpiatto [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wscgpz64.fsf@tux.homenetwork \
--to=thierry.volpiatto@gmail.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.
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.