From kde-core-devel  Thu Jan 26 07:55:41 2006
From: Boudewijn Rempt <boud () valdyas ! org>
Date: Thu, 26 Jan 2006 07:55:41 +0000
To: kde-core-devel
Subject: Re: Proposal to plan for "Milestone Releases" on the way to KDE4
Message-Id: <200601260855.42143.boud () valdyas ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=113826491315249
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1375544.zkhzT3cyGO"

--nextPart1375544.zkhzT3cyGO
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Thursday 26 January 2006 00:40, Alexander Dymo wrote:

> I've been watching at core KDE developers for three years. They still use
> vi (emacs). Why? Looks like KDevelop doesn't have clear benefits as
> a development tool for them. This is, of course my opinion and I'd really
> like to hear from KDE developers what they think is wrong in KDevelop.

I'm not really a core KDE developer, but I spend about forty hours a week=20
coding on Krita and KOffice, and I use KDevelop -- but only small parts of=
=20
it.

I don't compile from kdevelop, can't get used to it, I don use documentatio=
n=20
from kdevelop, I don't use the automake manager: I don't use all the things=
=20
on the left or right-hand fringe and it irritates me that I cannot disable=
=20
them. I don't debug from kdevelop -- never got it to work. I use qt: and kd=
e:=20
from the minicli for documentation.

In fact I use kdevelop over and above XEmacs (my previous favourite) for ju=
st=20
a few reasons:

* I can have the menubar on top of the screen instead of in the window itse=
lf.
* quick-open is handier than opening files in XEmacs
* autocomplete, broken and incomplete as it is is still handy (although I
  wish it wouldn't try to autocomplete every word in a comment with all of =
the
  symbols it knows)
* searching in multiple files works nicely
* indentation while typing works just as well as in XEmacs
* it supports unicode, which has become vital now that there are files
  created by G=E1bor Lehel in Krita.
* I can remember the shortcut to switch between header and implementation,=
=20
  which I never succeeded to do in XEmacs.

And I still use XEmacs to correct the indentation of an entire file, becaus=
e=20
kdevelop can't do that, and I still use vi when I need to make a quick edit=
=2E=20
KDevelop takes so long to start that I only use it when I know I've got mos=
t=20
of the evening for coding. I sometimes miss the simple word completion of=20
XEmacs. I definitely miss being able to split the window, to the extent tha=
t I=20
often have a konsole with vi alongside kdevelop.=20

But I'm a very simple-minded user. I never take the time to thoroughly lear=
n=20
anything: as soon as I can do what I want to do I stop investigating. Which=
=20
means that I use kdevelop as an editor with a bit of code completion and
the shell to compile, just like I did when I was an XEmacs, a vi, a Nedit o=
r a=20
Jed user.

Oh, and I use kdevelop only for C++. Python is better handled by XEmacs and=
=20
Java by Eclipse.

=2D-=20
Boudewijn Rempt=20
http://www.valdyas.org/fading/index.cgi

--nextPart1375544.zkhzT3cyGO
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBD2IB+daCcgCmN5d8RAmhYAKCS4g+MSEYemTIjsIcx/bLIZJhMFQCgswpJ
x89T3CjXmu/WKjN1Ss4wiYE=
=GC+t
-----END PGP SIGNATURE-----

--nextPart1375544.zkhzT3cyGO--