From: kidologie <richwellum@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Converting from compile-internal to compilation-start
Date: Thu, 8 Jan 2009 12:38:55 -0800 (PST) [thread overview]
Message-ID: <6aed703c-e4b2-4d29-b0c1-39566f33196f@n33g2000pri.googlegroups.com> (raw)
In-Reply-To: mailman.4338.1231428224.26697.help-gnu-emacs@gnu.org
On Jan 8, 10:24 am, Kevin Rodgers <kevin.d.rodg...@gmail.com> wrote:
> 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
Hmm had problems:
compilation-buffer-name: Wrong number of arguments: #[nil "À‡" ["rt-
nits"] 1 "rt-nits"], 1
I did:
(compilation-start (concat "/auto/eigrp/bin/nits -emacs " command)
nil #'(lambda (mode-name) "*rt-nits*"))
And that worked fine - I just pulled it as an example from the emacs
source - without understanding why it's happy.
Which brings me to another point with the new compilation-start - why
am I forced to enter a mode - as in your example - 'grep-mode? In my
cases I'm just kicking off a unix script under the covers and it
doesn't below to any particular mode..
Thanks!
next prev parent reply other threads:[~2009-01-08 20:38 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
[not found] ` <mailman.4338.1231428224.26697.help-gnu-emacs@gnu.org>
2009-01-08 20:38 ` kidologie [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6aed703c-e4b2-4d29-b0c1-39566f33196f@n33g2000pri.googlegroups.com \
--to=richwellum@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.
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.