From: "Drew Adams" <drew.adams@oracle.com>
To: "'Valentin Jacquemin'" <jacqueminv@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: Organizing files in projects
Date: Thu, 22 Apr 2010 09:34:21 -0700 [thread overview]
Message-ID: <5E076118F9AA40A2877727397DBE11C9@us.oracle.com> (raw)
In-Reply-To: <r2oa95535ca1004220558n2d1de6e8i5308b9d82a2c8c0c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
I don't think there is a single "almighty solution". There are many tools and
features that can help with code management, depending on what your needs are.
Here are some suggestions:
*
Search for "project" on Emacs Wiki.
*
Among other things, Emacs tags and Bookmark+ tags can help.
*
http://www.emacswiki.org/emacs/Icicles_-_Support_for_Projects
Others will offer additional pointers no doubt.
There are many ways to manage "projects" of code, and Emacs offers many features
that can help with this. It's up to you to decide how you want to do things and
which features are most useful for your needs.
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?
[-- Attachment #2: Type: text/html, Size: 2734 bytes --]
next prev parent reply other threads:[~2010-04-22 16:34 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 [this message]
2010-04-22 16:45 ` Nicolas Forgerit
2010-04-22 16:50 ` Richard Riley
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5E076118F9AA40A2877727397DBE11C9@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=jacqueminv@gmail.com \
/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.