From: "Alex Bennée" <kernel-hacker@bennee.com>
To: Robert Thorpe <rt@robertthorpeconsulting.com>
Cc: help-gnu-emacs@gnu.org, Marcin Borkowski <mbork@wmi.amu.edu.pl>
Subject: Re: I'm looking for a project management system for Emacs
Date: Thu, 03 Apr 2014 14:14:11 +0100 [thread overview]
Message-ID: <87a9c2sggs.fsf@bennee.com> (raw)
In-Reply-To: <87ioqr42gg.fsf@robertthorpeconsulting.com>
Robert Thorpe <rt@robertthorpeconsulting.com> writes:
> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>
>> A toolbox of features to combine into a tailor-made solution is fine
>> for me. Especially that my requirements might not be exactly common
>> (especially the scattering of the "project" files around many
>> directories).
>
> You could write some simple functions like this:
>
> (defun project1 ()
> (interactive)
> (find-file "project1/*" t)
> (find-file "elsewhere/randomfile.txt")
> (find-file "..."))
>
> (defun project2 ()
> (interactive)
> (find-file "project2/*" t)
> (find-file "project1/foo.txt"))
>
<snip>
That's sort of the approach eproject takes. You define a generic project
template and then it can apply the same rules to any instance of that
project. e.g:
;; QEMU
(define-project-type qemu
(generic-git)
(look-for "qemu-log.c")
:c-style "qemu-c-style")
(add-hook 'qemu-project-file-visit-hook 'my-eproj-is-c)
(add-hook 'qemu-project-file-visit-hook 'whitespace-mode)
--
Alex Bennée
next prev parent reply other threads:[~2014-04-03 13:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 6:56 I'm looking for a project management system for Emacs Marcin Borkowski
2014-03-29 9:35 ` Thorsten Jolitz
2014-03-29 18:12 ` Marcin Borkowski
2014-03-29 15:22 ` Drew Adams
2014-03-29 18:21 ` Marcin Borkowski
2014-03-29 18:24 ` Jai Dayal
2014-03-29 19:02 ` Drew Adams
2014-04-02 12:31 ` lee
2014-04-10 12:12 ` Jude DaShiell
2014-04-03 1:38 ` Robert Thorpe
2014-04-03 13:14 ` Alex Bennée [this message]
2014-03-29 20:45 ` Renato
[not found] <mailman.18471.1396076481.10748.help-gnu-emacs@gnu.org>
2014-03-29 17:11 ` Dan.Espen
2014-03-29 18:03 ` Marcin Borkowski
[not found] ` <mailman.18509.1396116232.10748.help-gnu-emacs@gnu.org>
2014-03-30 4:29 ` Dan.Espen
2014-03-30 8:06 ` Marcin Borkowski
[not found] ` <mailman.18551.1396166787.10748.help-gnu-emacs@gnu.org>
2014-03-30 14:18 ` Dan.Espen
2014-03-30 19:14 ` Marcin Borkowski
2014-03-31 17:34 ` hubert
[not found] ` <mailman.18567.1396206860.10748.help-gnu-emacs@gnu.org>
2014-03-30 20:30 ` Dan.Espen
2014-03-30 21:02 ` Marcin Borkowski
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=87a9c2sggs.fsf@bennee.com \
--to=kernel-hacker@bennee.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
--cc=rt@robertthorpeconsulting.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.
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).