From: bhoel@despammed.com (Berthold Höllmann)
Subject: Re: Making M-X compile cache compile command across sessions?
Date: Sun, 29 Jan 2006 19:30:41 +0100 [thread overview]
Message-ID: <m2d5iaubse.fsf@pchoel.psh> (raw)
In-Reply-To: drdaas$89r$1@panix2.panix.com
roy@panix.com (Roy Smith) writes:
> I'm working in a system which has longish compile commands, for
> example, "cd /work/smithr/sandbox/B-IC-6-2/smarts/clsapi; gmake
> BV=SUFFIX=V65".
>
> It's a pain to type all this every time I start up a new emacs
> session. I know I can setq compile-command in my .emacs file, but
> that's a little too static. It would be cool if emacs wrote the last
> compile command I used out to a file so it has a persistant cache
> across emacs sessions. Any way to make it do that?
>
> I'm using GNU Emacs 21.3.1.
I usually solve this via file variables. Usually you call this make
command when editin specific files. Let the files end with
;;; Local Variables: ***
;;; compile-command: "cd /work/smithr/sandbox/B-IC-6-2/smarts/clsapi; gmake BV=SUFFIX=V65" ***
;;; End: ***
and M-x compile provides you with the wanted default.
--
berthold@xn--hllmanns-n4a.de / <http://höllmanns.de/>
bhoel@web.de / <http://starship.python.net/crew/bhoel/>
prev parent reply other threads:[~2006-01-29 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 14:22 Making M-X compile cache compile command across sessions? Roy Smith
2006-01-28 0:30 ` Kevin Rodgers
2006-01-29 4:48 ` Ian Zimmerman
[not found] ` <mailman.91.1138510309.3044.help-gnu-emacs@gnu.org>
2006-01-29 13:56 ` Roy Smith
2006-01-29 18:30 ` Berthold Höllmann [this message]
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=m2d5iaubse.fsf@pchoel.psh \
--to=bhoel@despammed.com \
--cc=berthold@xn--hllmanns-n4a.de \
/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).