From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Converting from compile-internal to compilation-start
Date: Thu, 08 Jan 2009 08:24:02 -0700 [thread overview]
Message-ID: <gk55pj$49k$1@ger.gmane.org> (raw)
In-Reply-To: <cbc601f7-0da7-4050-83f9-8de8af85e2ea@r40g2000yqj.googlegroups.com>
kidologie wrote:
> Hello - after upgrading to emacs22, I see that compile-internal is now
> obsolete - I need to use compilation-start.
>
> What is the correct way to do this:
>
> (compile-internal (concat "nits -emacs" command)
> "All done" "rt-nits" nil grep-regexp-alist)
>
> using compilation-start?
Try
(compilation-start (concat "nits -emacs" command)
'grep-mode (lambda () "rt-nits"))
--
Kevin Rodgers
Denver, Colorado, USA
next prev parent reply other threads:[~2009-01-08 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 21:13 Converting from compile-internal to compilation-start kidologie
2009-01-08 15:18 ` kidologie
2009-01-08 15:24 ` Kevin Rodgers [this message]
[not found] ` <mailman.4338.1231428224.26697.help-gnu-emacs@gnu.org>
2009-01-08 20:38 ` kidologie
2009-01-10 3:04 ` Kevin Rodgers
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='gk55pj$49k$1@ger.gmane.org' \
--to=kevin.d.rodgers@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).