faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Model KWrite after GEdit, keep Kate for geeks
by Ilyak on Tuesday 15/Apr/2008, @11:29
|
Oh, nevermind, I've missed your point entirely.
I don't see why there's kate and there's kwrite. You're prodadly right, however we'll need to ask people who actually use kwrite.
Also: it would be cool if kwrite could embed into konqueror as textarea. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Model KWrite after GEdit, keep Kate for geeks
by Stefan Majewsky on Tuesday 15/Apr/2008, @12:01
|
I use Kate for projects which involve sets of multiple files which do not change rapidly, while KWrite is my choice for editing single files one time to not mess up my Kate defaults. Also, I have different defaults for indentation in Kate and KWrite because of the different use cases.
> Also: it would be cool if kwrite could embed into konqueror as textarea.
Yes, please! I hate this Embedded "Advanced" Text Editor without any real editing facilities.
|
[
Reply To This | View ]
|
Re: Model KWrite after GEdit, keep Kate for geeks
by Niklas on Tuesday 15/Apr/2008, @16:00
|
Yup, i'm too using both, kwrite and kate, in just the same workflow .
Btw. it would really nice to have a Tree-View file system pane in kate, like quanta has.
|
[
Reply To This | View ]
|
Re: Model KWrite after GEdit, keep Kate for geeks
by Stefan Monov on Wednesday 16/Apr/2008, @10:02
|
> I hate this Embedded "Advanced" Text Editor without any real editing facilities.
http://websvn.kde.org/trunk/KDE/kdebase/apps/konqueror/IDEAS?revision=659583&view=markup
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|