The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: vi rox!
by Ivo Anjo on Monday 24/Mar/2008, @15:40
|
I like kate because I use it for a lot of stuff, and lots for languages, many of which kdevelop doesn't support, so it is lighter and easier to use.
But I *really* loved the way kate worked a few releases back, where when you clicked on a file or opened one on the shell the same kate instance was re-used, instead of opening a new one.
I don't want to troll, and I know this has been discussed several times in bug reports and on the ML, but just wanted to say, I used it, I loved it, and I miss it :)
|
[
Reply To This | View ]
|
Re: vi rox!
by Anon on Tuesday 25/Mar/2008, @01:54
|
"kate -u" does the job.
You can also define an alias such as:
alias kt='kate -u'
and use it like this:
kt *.cpp
|
[
Reply To This | View ]
|
Re: vi rox!
by Ian on Tuesday 25/Mar/2008, @07:11
|
True, but the default usage should be open the selected file straight away, not have a session choice. Entering "kate -u" is not obvious to users who are not technical/*nix literate.
|
[
Reply To This | View ]
|
Re: vi rox!
by Kerr Avon on Tuesday 25/Mar/2008, @16:57
|
Yes, I would like to see Kate return to this behavour as well.
|
[
Reply To This | View ]
|
|
Re: vi rox!
by Morty on Monday 24/Mar/2008, @16:51
|
The fact that you are working with multiple files doers not necessary mean you are working on a project. Or if you do, it's not given that a KDevelop (or Quanta) project is up to the task. Sometime you want a editor able to handle multiple files, without the overhead of project management. For instance when you are working on bigger projects, or parts of such, like KDE, Linux kernel or something like uClinux. Sometimes you are only interested in working on a subset of the files, and very often there are no KDevelop project file.
|
[
Reply To This | View ]
|
Re: vi rox!
by jospoortvliet on Monday 24/Mar/2008, @22:42
|
Indeed. I use Kate to write the articles during KDE meetings, and it rocks. KDevelop isn't really what I'm looking for, as you can imagine...
|
[
Reply To This | View ]
|
|
Re: vi rox!
by Vide on Tuesday 25/Mar/2008, @01:35
|
Probably that there are lots of sysadmins using it to edit scripts or config files :P I mean, not everyone is a developer
|
[
Reply To This | View ]
|
I use Kate for...
by Kyle Horne on Tuesday 25/Mar/2008, @05:26
|
I use Kate for Fortran development, and small C and Python projects as well. I have tried many other tools, but I find that I like the simplicity that Kate provides, but still has a nice interface and many features.
At the university I attend and study mechanical engineering, many of my peers have to develop on the linux clusters for just a few of their projects, so they don't know linux very well. After I introduce them to Kate and how to start it through an X11 tunnel, they tend to use Kate almost like a universal interface to the cluster. It has a terminal, it has file editing, and file management too, so it fills all of their needs in one program. Not what it was intended for, but it still seems to work well for them.
|
[
Reply To This | View ]
|
Re: I use Kate for...
by Otter on Tuesday 25/Mar/2008, @10:17
|
Same here -- for small Python projects that don't require the full IDE machinery, I love the speed and simplicity of Kate. Plus I can usually count on it being available in a typical Linux system, which is rarely the case for KDevelop.
|
[
Reply To This | View ]
|
|
Re: vi rox!
by DominikH on Tuesday 25/Mar/2008, @07:37
|
I should have mentioned that Kate consists of several parts:
1. Kate Editor Component, also called Kate Part
2. Kate Application, also called Kate
KDevelop uses the Kate Part. The meeting of course also focuses on the Kate Part. All applications using the Kate Part benefit automatically if it improves.
|
[
Reply To This | View ]
|
Re: vi rox!
by Uwe Thiem on Tuesday 25/Mar/2008, @10:34
|
I use vi(m) when doing remote system or network administration.
Kwrite is my tool of choice when I write plain text documents that I will later copy-and-paste to some web sites or email around or some such.
Fully fledged kate is it when I hack on code. I don't want a complete IDE.More often than not, it gets in my way. The minimalistic project management kate offers is exactly what I want. So that is its role from my POV.
Uwe
|
[
Reply To This | View ]
|
Re: vi rox!
by Grósz Dániel on Tuesday 25/Mar/2008, @12:24
|
KDevelop uses a very fix project file/directory structure, not useful in many cases.
|
[
Reply To This | View ]
|
Re: vi rox!
by Martin Fitzpatrick on Tuesday 25/Mar/2008, @13:20
|
I think that's where I ran into problems when I tried to use it. I only do PHP development at the moment (websites and plugins for WordPress) and find Kate + Sessions a really simple way to get to what I want quickly - and also switch from one "project" to another mid-stream when I get an idea*...
(* have an episode of poor focus)
|
[
Reply To This | View ]
|
|
Re: vi rox!
by Chaoswind on Wednesday 26/Mar/2008, @11:41
|
> For editing multiple files at a time (which itself it means you're
> working on a project) there is Kdevelop
Kdevelop sucks. It's just a more complicated version of kate. Of cource, if you're developing with c/c++/qt, it's useful, but for every thinks else there is'nt any advantage. And now, that kdevelop3 has only this stupid spacewasting simple simpleIDEA-UI left, there is'nt any reason to use it.
I'm developing mostly python and pyqt-apps and use all the time kate. Of cource, kate sucks as well, but less. The UI can be minimalistic, and most of the missing features can be substitute with some nice scripts.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
