As long as an “off-topic” post to the planet is *short*, I don’t mind it. I predict the same community expectations in the Emacs IRC channel apply — celebrate off-topicalitiness.

Then escreen could be extended to support some more “screen” local settings, I’ve read, so I think you could handle a M-x compile history per screen and compile window. Ditto for find-tag. That’s the way I’d go if I was using M-x compile

Note I have extensive tools atop projects.el to ease the setup, and some escreen setup to share too. Ask if you’re interrested.

I’m torn between statically defining projects as mk-project does or defining types of project like eproject does. What I like about the second approach is the ability to define a project that looks for certain files (e.g. “AndroidManifest.xml”) and then automatically pick up the settings and attributes for a generic Android project.

Is it possible to emulate that behaviour with mk-project or is it orthogonal to the design?

Cheers,
Matt

Let’s you easily define projects with etags, ack, and grep support. Everything’s done succintly in elisp and loaded quickly with a couple keystrokes.

I just use them to redefine compile-command to run unit tests from the project’s root directory, and set tags-file-name to the correct TAGS file.