From: Elf M. Sternberg <elf@drizzle.com>
Subject: Re: Is emacs helpful or necessary to gcc programming?
Date: Mon, 09 Jun 2003 09:53:13 -0700 [thread overview]
Message-ID: <m3d6hn5h1i.fsf@drizzle.com> (raw)
In-Reply-To: jimkkREMOVEME-237BE5.16564931052003@visonmassif.rs.itd.umich.edu
Jimmerr <jimkkREMOVEME@umich.edu> writes:
> In article <873ciux2mn.fsf@helicon.physics.colostate.edu>,
> Dave Steffen <steffend@lamar.colostate.edu> wrote:
>> It just so happens that Emacs has very good support for programming,
>> which makes it _easier_ to write code.
> Thanks. I was referring to things such as being able to debug and
> compile from within emacs. Is this important?
Is it "important?" No. Is it nice? Absolutely. So is
automatic code indenting and face (changes to the color or style of a
display of characters depending upon their role' in the program). With
additional tools, emacs, like most good code editors, can help you
organize your build process and so on. Emacs makes it easier to debug
the blank file (which is all programming really is), but it's no more or
less "important" for that reason.
Elf
next prev parent reply other threads:[~2003-06-09 16:53 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 [this message]
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
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=m3d6hn5h1i.fsf@drizzle.com \
--to=elf@drizzle.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).