I didn't know this text editor..
Thanks for your hint, I'll have to try it, although I'm used to vim.

About my problems with Curses::UI
I wasn't able to clear keybindings like documented in Curses::UI::Widget.
Instead of e.g., as documented, 
$w->set_binding( \&myfunc, "\cF" );
$w->clear_binding( \&myfunc );

[download]
you'll have to call  $w->clear_binding( '__routine_'.\&myfunc ); In order to clear the binding to myfunc.

I had to look into the sources to figure this out, and I'd consider this a bug.. It should be at least documented in the pod.

I've mailed the maintainer, but didn't get an answer yet.

Next problem I had: the texteditor isn't searchable.
I tried to set some bindings to the according search functions,
but ended in a mess.
This time I wasn't able to figure out howto make the texteditor searchable within some hours, I gave up.

I'd like to say that Curses::UI are great modules as long as you don't want something too complex.

I personally also hate to do workarounds (which drives me crazy if I've to code some javascript..),
so I concluded that I'd be better with writing my own ui than using Curses::UI.

It's not the way I have fun, and I'd also like to say you'll end up in a mess.
Furthermore I believe such workarounds would become too dependent on the internals of Curses::UI. If anything changes in these modules, the workarounds could easily break.

Update: My feelings about getting into trouble with Curses::UI have been confirmed.
I just found this node: Re: text mode screen-oriented application development]
To quote Withigo: Debugging little quirks in Curses::UI which required custom overrides with Curses code was an especially painful.

In reply to Re^2: console editor by misc
in thread console editor by misc

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.