From: Martin Langhoff <martin.langhoff@gmail.com>
To: Howard Miller <howard@e-learndesign.co.uk>
Cc: "Daniele Segato" <daniele.bilug@gmail.com>,
"John Tapsell" <johnflux@gmail.com>,
"Frank Münnich" <git@frank-muennich.com>,
git@vger.kernel.org
Subject: Re: What IDEs are you using to develop git?
Date: Mon, 31 Aug 2009 12:21:00 +0200 [thread overview]
Message-ID: <46a038f90908310321p4e709969o749eea69310e947b@mail.gmail.com> (raw)
In-Reply-To: <26ae428a0908301206s38b36901y6027486f0d780ebc@mail.gmail.com>
On Sun, Aug 30, 2009 at 9:06 PM, Howard
Miller<howard@e-learndesign.co.uk> wrote:
> With a bit of learning
> can can do most of the stuff that an IDE does, usually faster and with
> less fuss.
Ditto. And with a very modest screen size. Modern IDEs need a huge
monitor, and then more, just to show what they want to show you.
Not what you need.
So when working on webapps, I normally keep my editor (usually an
emacs variant) window small, and have lots of terminal windows tracing
relevant logs (webserver, db server) and 3~4 webbrowsers logged in as
different users.
When working on git itself, it's much easier -- as all you need is
your editor and your terminal to compile & debug so for a simple task
like git itself, an IDE might even work ;-)
cheers,
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2009-08-31 10:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 12:15 What IDEs are you using to develop git? Frank Münnich
2009-08-25 12:47 ` John Tapsell
2009-08-30 18:07 ` Daniele Segato
2009-08-30 19:01 ` Nicolas Pitre
2009-08-30 19:06 ` Howard Miller
2009-08-31 10:21 ` Martin Langhoff [this message]
2009-08-30 21:29 ` Robin Rosenberg
2009-08-31 8:29 ` Erik Faye-Lund
2009-08-31 8:11 ` Andreas Ericsson
2009-08-31 11:36 ` Rustom Mody
2009-08-25 12:49 ` Andreas Ericsson
2009-08-25 12:56 ` Boaz Harrosh
2009-08-25 14:06 ` Thell Fowler
2009-08-25 14:18 ` Jakub Narebski
2009-08-26 4:24 ` Jeremy O'Brien
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=46a038f90908310321p4e709969o749eea69310e947b@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=daniele.bilug@gmail.com \
--cc=git@frank-muennich.com \
--cc=git@vger.kernel.org \
--cc=howard@e-learndesign.co.uk \
--cc=johnflux@gmail.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 NNTP newsgroup(s).