public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sebastián Magrí" <sebasmagri@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] perfect IDE
Date: Tue, 17 Feb 2009 21:50:17 -0430	[thread overview]
Message-ID: <1234923617.15111.4.camel@silversword> (raw)
In-Reply-To: <20090217205122.2d8e1e70@osage.osagesoftware.com>

[-- Attachment #1: Type: text/plain, Size: 2290 bytes --]

El mar, 17-02-2009 a las 20:51 -0500, David Relson escribió:
> On Tue, 17 Feb 2009 16:05:08 +0000
> Andrei Hanganu wrote:
> 
> > helo group,
> > 
> > i've been trying the past 2-3 years to find the most usable and nice
> > ide for c/c++ code writing. I've been through vim/vim + plugins/emacs
> > + different modes/anjuta/kdevelop/codeblocks/eclipse/netbeans ...
> > every single one of them has at least one drawback.
> > 
> > In short words, i am looking for an ide that can do this:
> > - syntax highlighting
> > - autocomplete (on the fly, not on demand, and maybe smart? - identify
> > structures/classes )
> > - concurrent editing of multiple files (splitting)
> > - tabs or buffer list
> > - file browser
> > - project manager
> > - symbol list/browser current editing buffer
> > - regex search/replace
> > - flexible build options that include scons, not just makefile
> > - code folding (with detection of blocks)
> > - lightweight/ergonomic interface (i dislike space being occupied by
> > the bar that displays the line numbers, with a padding of 10px for
> > example)
> > 
> > i don't desire gdb or valgrind integration, but would be a +
> > 
> > does anyone know the answer to this ultimate question? I keep
> > comparing different editors with the microsoft's visual studio, that
> > is not by far as powerful as emacs but it just plain and simple does
> > the job. They will reach a milestone when the brackets matching will
> > actually work, but despite small inconveniences, i find it to be very
> > close to what i am looking for.
> > kdevelop also seemed very close to what i wanted, but somehow the
> > fonts or the dpi make it very "crowded", i get very little space for
> > the code. On the other hand netbeans is a good example of how the
> > interface should be arranged, but java driven ide tends to stop being
> > able to respond in tolerable time.
> > 
> > i am on the edge of despair, and i am willing to try even a commercial
> > solution.
> > Anyone had some very positive experience with a specific ide?
> > 
> > thanks,
> > Andrei
> 
> I've heard some good things about komodo, though it's not open
> source and I've not used it.
> 
> David
> 

There is also Openkomodo, its name says what it is.. :)

[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-02-18  2:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 16:05 [gentoo-user] perfect IDE Andrei Hanganu
2009-02-17 14:32 ` Dan Cowsill
2009-02-17 17:09   ` Andrei Hanganu
2009-02-17 19:30     ` Paul Hartman
2009-02-17 17:47 ` Hung Dang
2009-02-17 18:06 ` Dirk Uys
2009-02-17 20:32 ` Andreas Niederl
2009-02-19 12:59   ` Andrei Hanganu
2009-02-20 10:52   ` Geralt
2009-02-18  1:51 ` David Relson
2009-02-18  2:20   ` Sebastián Magrí [this message]
2009-02-20 13:43   ` Liviu Andronic
2009-02-20 17:14 ` Eduardo Gurgel

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=1234923617.15111.4.camel@silversword \
    --to=sebasmagri@gmail.com \
    --cc=gentoo-user@lists.gentoo.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