
Yakuake Skins by bvs 9 comments

Yakuake Skins by felixhummel

Text Editors by zaufi 29 comments

Text Editors by zaufi 29 comments

Text Editors by zaufi 29 comments
my JID is the same as email and can be found at my github user page. - Apr 26 2014

Text Editors by zaufi 29 comments
2. color scheme for kate can be found here: https://github.com/zaufi/kate-stuff/tree/master/schema I'll put my KDE color theme here as well, so you can get it :) -- watch for updates in that repo :) - Apr 26 2014

Text Editors by zaufi 29 comments

Text Editors by zaufi 29 comments
plz try again - Sep 29 2013

Text Editors by zaufi 29 comments
Please try to compile from git (will be included in a next release)... - Sep 29 2013

Text Editors by zaufi 29 comments
try this `locate kate/plugin.h` - Sep 29 2013

Text Editors by zaufi 29 comments
error has been fixed, tarball reloaded. - Dec 24 2012

Kate by aNordal 5 comments
just give me a mail where I can send some files for you... - Oct 09 2012

Kate by aNordal 5 comments
I've played w/ 2.1 version and still found few problems w/ it... Some of them are:
0) it is Ok to use a backslash to continue dependency list on a next line, but it displayed as error in that case:
some-target : dep1 dep2 ... depM \
<spaces-here> depN ... depZ
<-tab->@rules goes here
1) it is not required for target names to be the first symbol on a line
target-1-displayed-ok : blah
<spaces> target-2-not-higlighted : blah-blah
sometimes it is convinient to have indented target definitions due `if' conditions...
btw, even if target name is at position 0, the following snippet displayed incorrectly:
target: blah
<-tab-># empty rule... just target (deps) declaration...
<spaces> # just a comment w/ leading spaces...
2) static pattern rules are diplayed strange (see 4.12.1 of `info make`) -- I guess better to introduce a few types (attributes) for different kind of rule declarations
3) the following snippet has strange (incorrect) higlighting @ 2nd line:
foo:= a.c b.c c.c
bar:= $(foo:.c=.o)
4) the following snippet is valid, but displayed incorrectly:
all:;echo $(foo)
moreover if next line starts w/ leading spaces it will be displayed as error, which is obviously incorrect as well...
also here is a whishlist :)
* it would be neat to higlight special targets (like .PHONY, .DEFAULT, & etc)
* also it may helps to higlight predefined make variables (like MAKELEVEL, MAKEFILES, etc) to make 'em visually diferent than a usual one...
* "10.5.3 Automatic Variables" (like $@, $<, $(D), etc)
* maybe "10.3 Implicit Variables"
* it would be nice to reuse bash.xml somehow to higlight a rules...
- Oct 09 2012

Kate by aNordal 5 comments
1) I still can't see error highlighting when spaces mixed w/ tabs (particularly spaces before tabs in rule definition)
- Oct 08 2012

Various KDE 1.-4. Improvements by gmolina 153 comments
if not, is it possible to implement?? - Nov 26 2011

Kate by zaufi 4 comments

Kate by zaufi 4 comments

Kate by zaufi 4 comments
*) removed keywords: except, finally and xalloc [done in my first post]
*) removed strings highlighting in "outscoped" context (i.e. inside #if 0/#endif blocks) [done in my 1.44.3 version]
so this "release" just version increment to prevent official 1.46 to override mine 1.45.1... - Jan 26 2010

Kate by zaufi 4 comments

Various Stuff by dannya 30 comments
---
as I c it could work in 2 modes:
a) user -- install everything into user home .kde directory
b) system wide -- install everything into `kde-config --prefix` directory (not into hardcoded path... what is really suck) - May 13 2004