From: Thien-Thi Nguyen <ttn@gnu.org>
To: Rami A <rami.ammari@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Waiting on compilation to finish before executing another function
Date: Thu, 15 Aug 2013 23:14:00 +0200 [thread overview]
Message-ID: <871u5ur71j.fsf@zigzag.favinet> (raw)
In-Reply-To: <b649346a-04b4-4c86-a306-ae79f8f72c6e@googlegroups.com> (Rami A.'s message of "Thu, 15 Aug 2013 10:36:21 -0700 (PDT)")
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
() Rami A <rami.ammari@gmail.com>
() Thu, 15 Aug 2013 10:36:21 -0700 (PDT)
I tried experimenting with compilation-finish-functions but found out
that the functions added to the list will be executed after "every"
compilation. Since I use compile to search IDs "gid" I don't want to
refresh opened files on every search.
For the compilation that does the pull, set a buffer-local variable
to note the case. Then add to ‘compilation-finish-function’ a function
that does ‘revert-all-buffers’ only if indicated by that variable.
Actually, ‘compile’ normally sets a bunch of buffer-local variables
itself. For instance, you could check ‘compilation-arguments’.
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-08-15 21:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 17:36 Waiting on compilation to finish before executing another function Rami A
2013-08-15 17:48 ` Dan Espen
2013-08-15 17:53 ` Rami A
2013-08-15 18:04 ` Dan Espen
2013-08-15 18:11 ` Rami A
2013-08-15 18:41 ` Eli Zaretskii
[not found] ` <mailman.103.1376592065.10748.help-gnu-emacs@gnu.org>
2013-08-15 18:53 ` Rami A
2013-08-16 1:43 ` Stefan Monnier
2013-08-15 21:14 ` Thien-Thi Nguyen [this message]
[not found] ` <mailman.113.1376601089.10748.help-gnu-emacs@gnu.org>
2013-08-15 21:46 ` Rami A
2013-08-15 22:41 ` Rami A
2013-08-15 23:03 ` Rami A
2013-08-15 23:11 ` Óscar Fuentes
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=871u5ur71j.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=rami.ammari@gmail.com \
/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).