unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jorgen Grahn <grahn+nntp@snipabacken.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs as a C Programming IDE Configuration?
Date: 9 May 2011 12:53:44 GMT	[thread overview]
Message-ID: <slrnisfoun.gtj.grahn+nntp@frailea.sa.invalid> (raw)
In-Reply-To: ic4o54eeez.fsf@verizon.net

On Mon, 2011-05-09, despen@verizon.net wrote:
...
> Anyway, just about everything I do is Makefile based.  I see lots of
> people use Makefiles for the compile phase but I find  that the test
> phase is intricately linked to the development phase and I combine both
> operations.

Agreed. "make check" should rebuild the automated tests if needed, and
execute them.

> It works for me and it works well, so I'll continue to push the viewpoint
> unless someone can explain why it's better to jump into M-x shell and
> start firing off random commands

That's quite a big leap from "the Makefile should run the unit tests"
to "there is nothing you may want to do in a shell".

> as if they may never have to issue them again

Modern shells (at least tcsh, bash and zsh) have persistent history
and incremental search.  I rarely have to type a complex command
from scratch, if I did something similar in the past few weeks.

/Jorgen

-- 
  // Jorgen Grahn <grahn@  Oo  o.   .  .
\X/     snipabacken.se>   O  o   .


  reply	other threads:[~2011-05-09 12:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  6:47 Emacs as a C Programming IDE Configuration? haziz
2011-04-27  9:11 ` Jorgen Grahn
2011-04-27 16:04   ` despen
2011-04-28  6:26     ` Jorgen Grahn
2011-05-09  1:38     ` David Combs
2011-05-09  1:42       ` Pascal J. Bourguignon
2011-05-09 16:30         ` Ted Zlatanov
2011-05-09 16:52           ` Pascal J. Bourguignon
2011-05-21 23:27           ` David Combs
2011-05-22  0:17             ` Pascal J. Bourguignon
2011-05-22 18:47             ` Stefan Monnier
2011-05-22 19:35               ` Jorgen Grahn
2011-05-23 14:50             ` Ted Zlatanov
2011-05-09  3:33       ` despen
2011-05-09 12:53         ` Jorgen Grahn [this message]
2011-05-26 14:56     ` Richard Riley
2011-05-26 14:54   ` Richard Riley
2011-04-27 18:26 ` Colin S. Miller
2011-04-30  0:07   ` haziz
2011-04-29 12:21 ` hjuvi
2011-05-02  3:24   ` rusi
2011-05-02  8:44     ` hjuvi
2011-05-02  9:29       ` Re : " hjuvi
2011-05-26 13:50 ` Richard Riley

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=slrnisfoun.gtj.grahn+nntp@frailea.sa.invalid \
    --to=grahn+nntp@snipabacken.se \
    --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).