From: Oliver Gerlich <olig9@gmx.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ?off? ide/code editor under linux
Date: Sun, 06 Aug 2006 18:21:17 +0200 [thread overview]
Message-ID: <44D616FD.30504@gmx.de> (raw)
In-Reply-To: <op.tdt9smcut9pcbo@mail.chello.hu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NyOS schrieb:
> Hi!
>
> I think it might be a bit offtopic here, but I'm already on the list,
> and I'm interested in some experienced users' opinion.
> I can find ads on google, but not experience.
>
> I'm looking for a good IDE (or just a good code editor) under linux.
> My first try was kdevelop approx. 3 years ago (2.2.2 version). It was
> too complicated. 3.x.x is a bit unstable.
> Vi is unconfortable for me,
> I prefer using pico and gnu nano, but it's too stupid for some tasks.
kdevelop is quite nice, but has some bugs, and shortcomings. If you're
looking just for an editor, I would recommend kate (which I use for
daily work, whenever I don't need a big IDE). It can be extended with
plugins and scripts, so maybe you could write a script to do the
template stuff.
Also, AFAIK Gnome's gedit can be extended with Python scripts, which
might be even better than the shell script / C++ plugin solution of kate.
Regards,
Oliver
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFE1hb7TFOM6DcNJ6cRAu4QAJ9Xu2TKuri9Uv//p+3kj1zrLEFsQgCgjQnH
y8FFrBhPJw4gFGk7E3YgCCc=
=Z+Bp
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-08-06 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 1:44 [Qemu-devel] ?off? ide/code editor under linux NyOS
2006-08-06 3:52 ` M. Warner Losh
2006-08-06 5:55 ` NyOS
2006-08-06 11:13 ` Thomas Steffen
2006-08-06 16:21 ` Oliver Gerlich [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44D616FD.30504@gmx.de \
--to=olig9@gmx.de \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.