From kde-core-devel Thu Jan 26 02:35:13 2006 From: Michael Pyne Date: Thu, 26 Jan 2006 02:35:13 +0000 To: kde-core-devel Subject: Re: Proposal to plan for "Milestone Releases" on the way to KDE4 Message-Id: <200601252135.29225.michael.pyne () kdemail ! net> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=113824242213787 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1395152.VVeWVYUQnp" --nextPart1395152.VVeWVYUQnp Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 25 January 2006 19:57, Alexander Dymo wrote: > > So yeah, when i'm working in konsole, I open my emacs, it opens pretty > > quickly and once it's open i never move my hands from the keyboard. > > That's just extremely convenient and I think that's /one/ of the main > > reasons why people still use emacs/vi. > > Ok. I agree on the mouse thing. Even when I forget what vim command does=20 something, I can type ":help some-word" from the keyboard and see if vim ca= n=20 point me in the right direction. > > Workflow using those editors is very different. > > Could you please give several things you frequently do in vi/emacs? 1. Opening the header for a file in a split window. Usually this is to see= =20 the API or documentation for a function (for which the intelligent tooltip= =20 feature in KDevelop would be nice if it would ever work), but sometimes it = is=20 in order to find a enum declaration or just something else in general=20 instead. 2. :%s/foo/bar/g is ever popular. (%s means search-and-replace over all=20 lines. The /g modifier at the end makes vim search and replace multiple=20 times in the same line). A Gui tool makes sense for this when s/foo/bar/=20 isn't what you want. But 95% of the time s/foo/bar/ is what you want, and = so=20 having to open a dialog is a chore, not a help. 3. I very often leave vim in order to run make. ;) It is quick to exit and= =20 quick to return to a file, in the position that I left it. 4. Another thing I'll do in vim is to mark a line that I'm at (using=20 'm'), go somewhere else, and quickly return to where I was by using= =20 "'". That is, the apostrophe key followed by the mark letter I=20 selected earlier is all I have to type. This lets me have multiple marks a= nd=20 quickly switch between them. I'm pretty sure there is something like this = in=20 KDevelop, but the interface takes too much time. These are all features built into vim, without the extra support scripts=20 available in kdesdk/scripts that I don't use. I mean, I'd like to use=20 KDevelop, but as you mentioned, it seems to not really mesh with my workflo= w. It was (and still is) cool for quickly starting new projects. But a lot of= =20 the features didn't live up to their promise when I tried it. For example,= =20 the API auto-completion didn't really work at all when I tried. The=20 documentation browser was a good idea, but had too much documentation (if=20 that makes any sense). I don't need all the G* and Java references when=20 writing a Qt app. ;) So I just used Konqueror in that case. I don't blame KDevelop for the compile times, but hopefully things will wor= k=20 better with the KDE 4 build system, when we finally get it finished and hav= e=20 apps starting to port against it. One thing that KDevelop has going for it is that the Kate guys know how to= =20 write a syntax highlighting engine. It is consistently better than vim's,= =20 especially with my kdesvn-build Perl script. But then, that helps everythi= ng=20 that uses KWrite, not just KDevelop. I'm afraid that pretty soon Kate may= =20 really be the KDE developer's preferred graphical IDE, and KWrite will be t= he=20 simple text editor. No offense to Anders on that, it's just that I still=20 want to be able to be more productive with KDevelop. It just doesn't seem = to=20 work out that way. Regards, - Michael Pyne --nextPart1395152.VVeWVYUQnp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBD2DVxqjQYp5Omm0oRAh4vAJsHzLvzHGuaG2o9C29kANqLmXLwxACeMHt8 nq8otGycBjiieL0sT5tlpdg= =1Zta -----END PGP SIGNATURE----- --nextPart1395152.VVeWVYUQnp--