I'm using nedit as my primary editor on my desktop. There's a command-line option for setting initial window geometry. I'm assuming that this will work for the Zaurus version, as well.
-geometry geometry (or -g geometry)
The initial size and/or location of editor windows. The argument geometry has the form:
[<width>x<height>][+|-][<xoffset>[+|-]<yoffset>]
thanks, I could now make nedit start up in an almost full-screen window using
alias n="nedit -g 61x17+0+0"
(the values for x and y are not pixels but characters!)
BTW, how long does nedit take to load on the Z? If it's fairly snappy, I may switch from Leafpad. For most tasks, however, I would be frustrated if there's a significant lag in opening.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143146\"][{POST_SNAPBACK}][/a][/div]
Here it takes about 10 seconds to load, so it is not as snappy as leafpad. But once it is loaded it is reasonably fast and well usable (after creating some macros to maike the cursor keys work as expected, see above).
Regarding the Umlauts:
I was wrong. The used font HAS the umlauts They are shown corectly when I load ISO-8859-1 coded files with nedit. But when pressing the key codes for Umlauts (Fn-a, Fn-o etc. on my system, works in Console and most other apps), no Umlauts are generated in nedit but rather two-byte character combinations. Looks a bit like a unicode problem, such as the keys generating unicode (two-byte) characters which nedit cannot display.
The Umlauts which are shown correctly are indeed no unicode Umlauts but ISO-8859-1 coding.
Any idea how I can make the keys work correctly in nedit? Possibly also using macros...
daniel