From: Dmitry Dzhus <dima@sphinx.net.ru>
To: help-gnu-emacs@gnu.org
Subject: Re: Multiple *compilation* buffers
Date: Fri, 31 Oct 2008 17:46:33 +0300 [thread overview]
Message-ID: <87prlgg6uu.fsf@sphinx.net.ru> (raw)
In-Reply-To: mailman.2567.1225462677.25473.help-gnu-emacs@gnu.org
John Paul Foster wrote:
> I dont want to ^ever^ leave emacs so is there a way to run multiple grep
> and/or compilation processes at once?
> Any ideas, or is this a question for the devel list?
You'll want to customize `compilation-buffer-name-function` variable.
Try to read documentation string for `compile` function.
--
Happy Hacking.
http://sphinx.net.ru
む
next parent reply other threads:[~2008-10-31 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2567.1225462677.25473.help-gnu-emacs@gnu.org>
2008-10-31 14:46 ` Dmitry Dzhus [this message]
2008-10-31 10:23 Multiple *compilation* buffers John Paul Foster
2008-10-31 14:52 ` Peter Dyballa
2008-11-01 13:36 ` Kevin Rodgers
2008-11-03 8:13 ` John Paul Foster
[not found] ` <mailman.2629.1225547112.25473.help-gnu-emacs@gnu.org>
2008-12-01 3:03 ` David Combs
2008-11-01 13:35 ` 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=87prlgg6uu.fsf@sphinx.net.ru \
--to=dima@sphinx.net.ru \
--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).