From: Roy Smith <roy@panix.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to pre-load compile command history?
Date: Wed, 16 Nov 2011 13:36:31 -0500 [thread overview]
Message-ID: <C2856F55-8830-413C-83F2-5A6E9E6335F6@panix.com> (raw)
In-Reply-To: <3135048E86744BFC9C3BAFA295F56AED@us.oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
Hmmm, my lisp is really rusty, and I'm struggling with the syntax. The following doesn't seem to work.
(setq compile-history (cons '("cd /home/roy/songza/pyza/djapi; python test_api.py"
"cd /home/roy/songza/code/radio/api/mobile/test; python test_api.py"
)
))
On Nov 16, 2011, at 12:54 PM, Drew Adams wrote:
>> (global-set-key "\C-cm" 'compile)
>> (setq compile-command "cd
>> /home/roy/songza/code/radio/api/mobile/test; python test_api.py")
>>
>> That works fine, but now I've got several different commands
>> that I run often. Is there some way to pre-load them into
>> the compile history, so I can just do c-c m, then up-arrow
>> though the history to pick the one I want?
>
> If option `compilation-read-command' is non-nil then you are prompted with
> completion for the compilation command to use. You can set the history variable
> `compile-history' ahead of time, so you can then use `M-n', `M-p', `M-s', and
> `M-r' to access the commands on your list.
>
> (This is according to what I see in the code in `compile.el'. I don't often use
> `compile' myself.)
>
---
Roy Smith
roy@panix.com
[-- Attachment #2: Type: text/html, Size: 5240 bytes --]
next prev parent reply other threads:[~2011-11-16 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 17:16 How to pre-load compile command history? Roy Smith
2011-11-16 17:54 ` Drew Adams
2011-11-16 18:36 ` Roy Smith [this message]
2011-11-16 19:08 ` Drew Adams
2011-11-17 1:11 ` Roy Smith
2011-11-16 19:58 ` Tom
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=C2856F55-8830-413C-83F2-5A6E9E6335F6@panix.com \
--to=roy@panix.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
/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.