Give it a shot, if you don’t like it, take it off, but I think you will. This is a bug in lesstif, and was never fixed, so it doesnt matter what lesstif versions you try. Note the different > versions of LessTif.
Both with Debian supplied binary, and with > binary compiled from source. I really wouldn’t mind if they stopped development as I’d use it until I found something better, but until that happens it suits my need and I didn’t see any harm in taking the few minutes it takes to compile and keeping it on my system. Logged In: YES userid918104 > Same bug here. Oh, BTW, there may be a new maintainer very soon, so dvp won’t stop stay in touch.įor a lot of projects it’s great, the features I like about it are 1) how light it is 2) the way the highlighting is 3) the tabs 4) It’s GTK2 and last but not least 5) the line numbers that it puts in down the side. And this time it REALLY is my last work on Beaver.
NEDIT BUGD WINDOWS
I tried both Windows and Linux X2Go clients, using nxproxy 3.5.0.x. Under X.org, it launches fine regardless of how it is built.
NEDIT BUGD DOWNLOAD
I just recently installed and re-grabbed the source, which I know is the same version I had last time.įrom the site I see: I needed another new feature… Guess what happened then ! As usual, Changelog and Download sections have been updated accordingly. NEdit segfaults on launch under X2Go with nxagent/x2goagent 3.5.0.32 or 3.5.0.99 b7657cf on my CentOS 7.2 test VM, but only when it is built with Motif rather than LessTif.
NEDIT BUGD FULL
(*) You have to self-compile NEdit with OpenMotif 2.2.3-4 to replace LessTif.I’ve not seen a new release in awhile, I didn’t really take a look at the full site. Maybe for someone else it provides a useful hint. Until restart of X11.įor me this is strange, not being familiar with X11-client-server topology. Numeric keypad is not working but also doesn't work with the local version of NEdit on the old machine. It "works" the other way around, also: Startup old machine and login via ssh to the new machine and invoke NEdit. Now invoke NEdit on the new machine and the numeric keypad works for the rest of the day! (Until restart of X11 actually). Numeric keys work as expected just like working locally on the old machine. Startup new machine and login via ssh to the old machine and invoke NEdit.
NEDIT BUGD CODE
Maybe using some "tricks", which may still be in the code and interfere with a recent Motif. In some later version of NEdit this was fixed. Ctrl-S did not save when one of the modifiers was on but inserted an control code like. This is the reason, why it behaves different.Ģ) I do recall in the early 2000s NEdit had some strange behaviours with CAPS-Lock and Numlock etc, so called "modifiers". IIRC it was derived from it some long time ago. I wonder why this bug affected only copying to NEdit, but fixing this (just doing " global replace" string " text/plain. QT3 just forces selection/clipboard text to be interpreted as ISO-8859-1 regardless of any locale settings.
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8)ġ) NEdit's text window is different from Motifs text widget. After spending long time digging in X, QT, lesstif and NEdit sources I realized that it is really QT3 bug, not NEdit. Probably becauseġ:5.6~cvs20081118-7 depend's on lesstif2, and later depend on libxm4. If I recompil wheezy version on jessie, it's ok. Wheezy nedit version is ok ( 1:5.6~cvs20081118-7 ) but not after (jessie, Matter whether the numlock is on or off ( with the exception of key "5") When using NEdit, I am unable to use the numeric keypad to enter numbers no