From: "Taylor Jones" <taylor.jones@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Setting the compile-command history in dotel files
Date: Wed, 5 Mar 2008 08:54:02 -0800 [thread overview]
Message-ID: <ee635b9d0803050854j71dc8f20t22fe723f13d0bbac@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
Currently I do M-x compile, type a custom compile command, then later do M-x
compile and run a different compile command. Then later I can do M-x compile
M-p to cycle through the history ring of previous compile commands. What I
would like to do is set this history ring upon startup though my dotel file.
Is this possible? Currently all I can do is set one compile command with
(custome-set-variables '(compile-command "compile_command_1"))
I tried playing with setting compile-command to a list of strings, but
couldn't get anything to work.
[-- Attachment #2: Type: text/html, Size: 585 bytes --]
next reply other threads:[~2008-03-05 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 16:54 Taylor Jones [this message]
2008-03-05 17:00 ` Setting the compile-command history in dotel files Peter Dyballa
2008-03-05 17:35 ` Joel J. Adamson
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=ee635b9d0803050854j71dc8f20t22fe723f13d0bbac@mail.gmail.com \
--to=taylor.jones@gmail.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.
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).