Kephra 0.4.3 released

[sir_lichtkind]

Because Kephra can now be safely installed from your local CPAN mirror, I make here some additional noise so you will think: "maybe I should try it?"(tm). Its fast and very stable (unless you find a bug of course). No kidding, some weird but harmless GTK warnings are recently the only known issue.

The obvious is already posted, headline and changelog.

R* gogogo

EDIT: as merlyn correctly pointed to, there was no information about Kephra and this update at all:

Kephra is a Texteditor that don't try to force. Nearly everything is customizable and/or optional. It can be used mostly with mouse or keyboard and soon even by an Vi like commandline. Our approach is more tight, effective, integrated, even if some Plugin API is there and half its purpose is to extend it quickly with Perl.

This release was importand to fix the most nagging problems with utf and the cpan installer. Code folding and bookmarks were finalized. We introduced marker, unlimited little markings that can be navigated also via searchbar. Syntaxchecker, debugger, search tools can use this feature. We added also a fullscreen, transparency and a kind of "netbook mode" which closes temporally all bars but tabbar (can even disable this) to get most of small screens. Esc closes all these modes. As always many small things and fixes come with every new release. Enjoy.

[wazoox]

Tests failed.... What can be wrong? I'll have a look at the code and come back.

  LICHTKIND/Kephra-0.4.3.0.tar.gz
  /usr/bin/make -j5 -j5 -- OK
Running make test
PERL_DL_NONLAZY=1 /usr/local/bin/perl "-MExtUtils::Command::MM" "-e" "
+test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/*.t
t/01_compile.t ......... 7/76 
#   Failed test 'require Kephra::Dialog::Exit;'
#   at t/01_compile.t line 43.
#     Tried to require 'Kephra::Dialog::Exit'.
#     Error:  Can't use bareword ("Kephra::Config::Localisation::strin
+gs") as a HASH ref while "strict refs" in use at lib/Kephra/Dialog/Ex
+it.pm line 39.
# Compilation failed in require at (eval 72) line 2.

#   Failed test 'require Kephra::App::Window;'
#   at t/01_compile.t line 43.
#     Tried to require 'Kephra::App::Window'.
#     Error:  Bareword "Kephra::App::MenuBar::get_visibility" not allo
+wed while "strict subs" in use at lib/Kephra/App/Window.pm line 123.
# Bareword "Kephra::App::MainToolBar::get_visibility" not allowed whil
+e "strict subs" in use at lib/Kephra/App/Window.pm line 125.
# Bareword "Kephra::App::SearchBar::get_visibility" not allowed while 
+"strict subs" in use at lib/Kephra/App/Window.pm line 129.
# Compilation failed in require at (eval 97) line 2.
# Looks like you failed 2 tests of 76.
t/01_compile.t ......... Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/76 subtests 
        (1 TODO test unexpectedly succeeded)
t/02_config.t .......... ok   
t/03_config_default.t .. ok   
t/10_new.t ............. ok

[sir_lichtkind]

thanks, i fixed that issues. its in code base from 0.3.4.1 on, just force for now..

[merlyn]

Announcement fail.

Not even half a sentence about what it is.

Please, when you announce things, don't make me follow a link just to even map a name to a general category.

[sir_lichtkind]

Allright fixed that, but there was a whole sentence, in the sig ! :)

[merlyn]

Many people have sigs blanked by CSS. Those who don't (like me) probably have learned to just skip over them mentally.

Do you really think I expect people reading my posts to go look up RFC 2119? No. The point of a sig is boilerplate. Not an integral part of the message.