From: Richard Riley <rileyrgdev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Organizing files in projects
Date: Thu, 22 Apr 2010 18:50:11 +0200 [thread overview]
Message-ID: <5bb6a7-5l3.ln1@news.eternal-september.org> (raw)
In-Reply-To: r2oa95535ca1004220558n2d1de6e8i5308b9d82a2c8c0c@mail.gmail.com
Valentin Jacquemin <jacqueminv@gmail.com> writes:
> Hi all,
>
> I use more and more emacs for my hacking activities. I am more used to Netbeans and Eclipse
> IDEs but the possibility to do anything from only one editor attracts me....
>
> One thing I miss however currently is the possibility to organize my files as a project.
> Typically if I develop a PHP application, I'd like to be able to a)navigate in the current
> file to jump directly to a class' member (either variable, function, whatever) and b) jump
> into a dependency, this can be a superclass or a class from a library I use, anything. Doing
> that from my beloved IDEs is very easy, but from Emacs I read about tags, anything and
> certainly others...
>
> My question is: is there an "almighty" solution?
>
> Thanks for your help,
>
> Valentin Jacquemin
>
Simple answer :no.
More complex : maybe.
Look up cedet. And tags. And global tags. And cscope. And .....
The most promising solution is cedet. It is pretty complex and I can't
comment on the maturity of the PHP parser.
Anything counts itself out from its awful UI imo. For completion I use
company-mode which has a cedet hook.
For navigation generally etags - exhuberant-ctags.
next prev parent reply other threads:[~2010-04-22 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 12:58 Organizing files in projects Valentin Jacquemin
2010-04-22 16:34 ` Drew Adams
2010-04-22 16:45 ` Nicolas Forgerit
2010-04-22 16:50 ` Richard Riley [this message]
2010-04-23 13:55 ` Joel J. Adamson
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=5bb6a7-5l3.ln1@news.eternal-september.org \
--to=rileyrgdev@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.
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).