From: pjb@informatimago.com (Pascal J. Bourguignon)
To: help-gnu-emacs@gnu.org
Subject: Re: Very simple IDE for programming newbie
Date: Sun, 03 Jan 2010 17:44:04 +0100 [thread overview]
Message-ID: <87eim7t9yj.fsf@hubble.informatimago.com> (raw)
In-Reply-To: m2ljgfqidd.fsf@sean-mcafees-macbook-pro.local.i-did-not-set--mail-host-address--so-tickle-me
Sean McAfee <eefacm@gmail.com> writes:
> pjb@informatimago.com (Pascal J. Bourguignon) writes:
>
>> Sean McAfee <eefacm@gmail.com> writes:
>> Also, for non-interactive programs, you can do it at once with:
>>
>> M-x compile RET C-e && ./this-file RET
>
> Hmm, good idea. I'm trying to look ahead to when we get to
> interactive programs too, though.
>
>> You don't have to wait for the end of the compilation to browse the
>> errors. Otherwise, just watch the status bar of the *compilation*
>> window, it will say (Compilation:exit [<status-code>]) when done.
>
> 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.
>
> I think the terminal emulator would be preferable to shell-mode, since
> in the former case there's only one keystroke that could introduce
> some confusion (C-c) and in the latter case there are many.
I would just do that:
M-x compile RET C-e && ( xterm -e ./this-file & ) RET
--
__Pascal Bourguignon__ http://www.informatimago.com/
next prev parent reply other threads:[~2010-01-03 16:44 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 [this message]
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
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=87eim7t9yj.fsf@hubble.informatimago.com \
--to=pjb@informatimago.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.