all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sean McAfee <mcafee@sean-mcafees-macbook-pro.local>
To: help-gnu-emacs@gnu.org
Subject: Re: Very simple IDE for programming newbie
Date: Sun, 03 Jan 2010 16:02:07 -0500	[thread overview]
Message-ID: <m2d41q6gxc.fsf@sean-mcafees-macbook-pro.local.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: mailman.662.1262546694.18930.help-gnu-emacs@gnu.org

Peter Dyballa <Peter_Dyballa@Web.DE> writes:

> Am 03.01.2010 um 17:10 schrieb Sean McAfee:
>> I know; my question was how to a) know when the asynchronous
>> compilation process has finished, and b) tell whether there were any
>> errors, so that if there were none, I can immediately launch the
>> newly-compiled program in a terminal emulator.
>
>
> The *compilation* buffer's mode-line expresses such things.

Actually, by "I" above I meant the special compilation function I'm
planning to write.  Something like:

(defun my-compile ()
  (interactive)
  (compile (format "gcc %s" (file-name-nondirectory (buffer-file-name))))
  (when-compilation-is-complete
   (lambda ()
     (when (not (there-were-errors))
       (kill-buffer "*term*")
       (term "./a.out")))))

What I'm not quite clear on at the moment is how to write the
when-compilation-is-complete and there-were-errors functions.

Actually, for there-were-errors I could obviously parse the content of
the *compilation* buffer, but I was hoping the same information might
be available more directly.


  parent reply	other threads:[~2010-01-03 21:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-02 18:51 Very simple IDE for programming newbie Sean McAfee
2010-01-02 21:07 ` Pascal J. Bourguignon
2010-01-03 16:10   ` Sean McAfee
2010-01-03 16:44     ` Pascal J. Bourguignon
2010-01-03 17:17     ` Richard Riley
2010-01-03 19:24     ` Peter Dyballa
     [not found]     ` <mailman.662.1262546694.18930.help-gnu-emacs@gnu.org>
2010-01-03 21:02       ` Sean McAfee [this message]
2010-01-03 21:49         ` despen

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=m2d41q6gxc.fsf@sean-mcafees-macbook-pro.local.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mcafee@sean-mcafees-macbook-pro.local \
    --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.