zaufi

any chance to get HiDPI version? (at least dbl sized) - Dec 26 2017

any chance to get HiDPI version? (at least dbl sized) - Dec 26 2017

any chance to get HiDPI version? (at least dbl sized) - Dec 26 2017

could you please use a bug tracker @ https://github.com/zaufi/kate-cpp-helper-plugin and provide a backtrace and compiler/dependencies versions. - Dec 15 2014

take a look to ATTENTION note at changelog of version 1.0.3 on this site or homepage, or read requirements in README. - Oct 14 2014

contact me via XMPP, I'll try to help you w/ compilation.
my JID is the same as email and can be found at my github user page. - Apr 26 2014

1. yeah, that package is for Ubuntu 13.10 ... I need to rebuild one for recently released 14.04 (I'll do it soon... after I've find a way to start my ubuntu repo w/ debs for varous distros). But you still can compile it from sources :)

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

please use issues tracker @ github.com to report details about compiler errors. the .deb already fixed in `master` and reloaded - Dec 14 2013

missed kate_export.h now in git repo.
plz try again - Sep 29 2013

I've just commited a fix for debian/ubuntu which do not have a package for required files (see issue #10 in project tracker).
Please try to compile from git (will be included in a next release)... - Sep 29 2013

make sure that kate developer files are installed.
try this `locate kate/plugin.h` - Sep 29 2013

Oops... sorry I played w/ clang 3.2 and forget to wrap it into #ifdefs...
error has been fixed, tarball reloaded. - Dec 24 2012

btw, I have some legacy project w/ a sophisticated makefile(s) (in fact a whole build system like autotools was implemented on pure makefiles), so you may play w/ higligting on it...

just give me a mail where I can send some files for you... - Oct 09 2012

Hi!

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

0) if comments (lines w/ '#' as first noncpace char) contains a ':' symbol they higlighted as targets (not as comments!)

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

is there any way to import passwords from FF storage to wallet?
if not, is it possible to implement?? - Nov 26 2011

It seems official version has started to move towards C++0x support! :) 'static_assert' is the only change since 1.47 (done in my 1.47.2), but to prevent override I have to issue 1.48.1 (w/ little changes :) - Jun 22 2011

s/1.44.3/1.43.2/ - Jan 26 2010

There is just couple of improvements since official 1.45:
*) 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

As far a I saw (using diff) recently released 1.44 version do not introduce anything new 'cept 'formatting' changes... - Apr 28 2009

... installation script is really suxx :(
---
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

$subj is required :) -- like 1280x1024 at least...
Splash screen will be nice too (especialy with some transparency effects :) - Dec 29 2003