From: Andrea Crotti <andrea.crotti.0@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Compilation buffer
Date: Thu, 25 Nov 2010 00:17:00 +0100 [thread overview]
Message-ID: <m1zksy8g7n.fsf@ip1-201.halifax.rwth-aachen.de> (raw)
I stole this nice trick somewhere
--8<---------------cut here---------------start------------->8---
(defun kill-compile-buffer-if-successful (buffer string)
(if (string-match "finished" string)
(run-with-timer 1 nil
'kill-buffer
buffer)))
(add-hook 'compilation-finish-functions 'kill-compile-buffer-if-successful)
--8<---------------cut here---------------end--------------->8---
And actually it's very nice, in short if the compilation succeeds the
buffer is killed, but there are two small problems:
- not just "compile" uses compilation mode, for example grep also does
but then the buffer disappears too soon.
Is there a way to distiguish between those different things?
- I would also like to see warnings if there are, so the "finished"
maybe it's not enough, here now other ways that just doing
"string-matching" right?
Another thing it would be nice is a way to jump, from everywhere, to the
next error/warning.
Now I have to
- go to the compilation buffer
- go to the next error
- press Enter
Is there some function already to automate it or should I create a macro/function?
next reply other threads:[~2010-11-24 23:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 23:17 Andrea Crotti [this message]
2010-11-24 23:32 ` Compilation buffer Burton Samograd
2010-11-25 7:12 ` Deniz Dogan
2010-11-25 14:34 ` Thien-Thi Nguyen
2010-11-25 16:57 ` Andrea Crotti
2010-11-25 21:05 ` Thien-Thi Nguyen
2010-11-25 23:22 ` Andrea Crotti
2010-11-26 6:59 ` Thien-Thi Nguyen
2010-11-29 4:42 ` Has anything thought of this before: having clipboard and deleted text separate Maindoor
2010-11-29 7:01 ` PJ Weisberg
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=m1zksy8g7n.fsf@ip1-201.halifax.rwth-aachen.de \
--to=andrea.crotti.0@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.