unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Pascal Bourguignon <spam@thalassa.informatimago.com>
Subject: Re: Is emacs helpful or necessary to gcc programming?
Date: 05 Jun 2003 19:32:49 +0200	[thread overview]
Message-ID: <87el28whtq.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: jimkkREMOVEME-7D5DA4.16191231052003@visonmassif.rs.itd.umich.edu

Jimmerr <jimkkREMOVEME@umich.edu> writes:

> If I use a different editor from emacs, what features will I be losing 
> in terms of programming with gcc?
> 
> Thanks
> Jim

As I've already written, you  don't program with gcc, you program with
your brains, your little fingers and an editor.


So  if the  question  is what  features  you would  lose  in terms  of
compiling with  gcc your C  programs, I'd say  none at all,  go ahead,
enter your C programs with a switch panel in binary!


Otherwise you must compare the features of emacs with those of another
editor and see  which one gives more for your bucks,  that is, for the
work of your fingers and of your brains.


-- 
__Pascal_Bourguignon__                   http://www.informatimago.com/
----------------------------------------------------------------------
Do not adjust your mind, there is a fault in reality.

      parent reply	other threads:[~2003-06-05 17:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-31 20:19 Is emacs helpful or necessary to gcc programming? Jimmerr
2003-05-31 20:49 ` Dave Steffen
2003-05-31 20:56   ` Jimmerr
2003-05-31 22:23     ` Ichimusai
2003-06-01 13:03     ` Jason Rumney
2003-06-01 18:29     ` Ole Laursen
2003-06-01 19:03       ` Dan Espen
2003-06-02  4:30     ` Dave Steffen
2003-06-09 16:53     ` Elf M. Sternberg
2003-06-01  6:12 ` Pascal Bourguignon
2003-06-02 13:18 ` Mark Mynsted
2003-06-05 15:00 ` Arnold
2003-06-05 17:32 ` Pascal Bourguignon [this message]

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=87el28whtq.fsf@thalassa.informatimago.com \
    --to=spam@thalassa.informatimago.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).