I actually used a small script to use symlinks for switching between the original nedit and the ng one. They are a drop-in replacement for “nc” and “nedit”. NEdit 5.7 that came with Ubuntu 18.04 and the binary that was perfectly stable under 16.04 (under ESXi) were both getting into state when the keyboard input wasn’t working (but Ctrl+ and functional keys still did). I had to start using nedit under Ubuntu 18.04.5 in VirtualBox under Win 10. ![]() The edit windows keyboard input problem though is certainly resolved now. It appears to work, but it has been only a week or so, not enough time to confirm for sure that the dialog boxes problem is gone. ![]() ![]() So far my solution was to link nedit statically under Ubuntu 16.04 (see “static-ubuntu16″ build configuration) where it worked flawlessly and run that executables under 18.04. I haven’t spent much time on the dialog boxes input problem yet. ![]() It solved the problem with the input into the edit windows, but introduced (or maybe they are unrelated) the problem with the dialog boxes. I had to start using nedit under Ubuntu 18.04.5 in VirtualBox under Win 10 and unfortunately encountered an intermittent problem with the keyboard input stopping to work (see post here: ).Īfter trying to use nedit-ng for a bit I decided to switch back and try to solve that keyboard input problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |