unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Compilation buffer
Date: Thu, 25 Nov 2010 15:34:14 +0100	[thread overview]
Message-ID: <87eia9jwux.fsf@ambire.localdomain> (raw)
In-Reply-To: <m1zksy8g7n.fsf@ip1-201.halifax.rwth-aachen.de> (Andrea Crotti's message of "Thu, 25 Nov 2010 00:17:00 +0100")

() Andrea Crotti <andrea.crotti.0@gmail.com>
() Thu, 25 Nov 2010 00:17:00 +0100

   I stole this nice trick somewhere

     (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 | ompile-buffer-if-successful)
                                                   | 
   And actually it's very nice, in short if the co | ilation succeeds the
   buffer is killed, but there are two small probl | s:
                                                   | 
   - not just "compile" uses compilation mode, for | xample grep also does
     but then the buffer disappears too soon.      | 
     Is there a way to distiguish between those di | erent things?
                                                   | 
The first arg to the function is the buffer. ------+
You can test that.



  parent reply	other threads:[~2010-11-25 14:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 23:17 Compilation buffer Andrea Crotti
2010-11-24 23:32 ` Burton Samograd
2010-11-25  7:12   ` Deniz Dogan
2010-11-25 14:34 ` Thien-Thi Nguyen [this message]
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

  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=87eia9jwux.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --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).