unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* compile-command directory local
@ 2003-04-27  2:11 Dan Jacobson
  0 siblings, 0 replies; only message in thread
From: Dan Jacobson @ 2003-04-27  2:11 UTC (permalink / raw)


I do M-x compile in dir1, and then dir2.
Emacs should have a variable that would enable keeping separate ideas
of what to prompt with for each current directory.
E.g. for this scenario
$ cd bugs
$ make kill
$ cd pets
$ make feed...
one just doesn't do ^RmakeRET... In emacs we can do better.
if one were just to hit RET to emacs' prompts, dead pets and fed bugs
are the result unless you implement my suggestion.

Yes, one could use local variables at the bottom of each makefile.  or
do (make-variable-buffer-local 'compile-command) but I'm afraid thus
is not achieving directory-wide control of compile-command.

Yes, if one were in Makefile when one calls compile, it might feel
that way, but often one is in other files of the same directory.

One could fiddle with compilation-mode-hook, but that would assume
were in the *compilation* buffer when we invoke compile.

I know, someone is going to send "advice" which I will stuff in my
.emacs file and my brilliant suggestion will thus wither in the mist.
-- 
http://jidanni.org/ Taiwan(04)25854780

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2003-04-27  2:11 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-04-27  2:11 compile-command directory local Dan Jacobson

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).