Evan Teran

@tringali, after re-reading your suggestion. i can say that i think yhe idea of: xnedit -> nedit-classic NG -> nedit makes sense to me and avoids most confusions since it makes it clear that classic is a continuation of the motif lineage while NG is a feature for feature port to create a new version

@tringali, after re-reading your suggestion. i can say that i think yhe idea of: xnedit -> nedit-classic NG -> nedit makes sense to me and avoids most confusions since it makes it clear that classic is a continuation of the motif lineage while NG is a feature for feature port yo create a new version

@efa, neditNG supports all platforms which Qt supports. this is at a minimum, Windows, Linux, and macOS. but in practice most unix-like OSes as well, including various BSDs. it's a highly portable library, i think even a Haiku port works, LOL. @tringali, I am kind of of two minds about your suggestion. of course I love the idea of reinvigorating the base and Nedit community by getting a 6.0 release out. but my only concern is that xnedit and NG are on somewhat divergent paths from a common ancestor....

@efa, neditNG supports all platforms ehich Qt supports. this is at a minimum, Windows, Linux, and macOS. but in practice most unix-like OSes as well. iys a highly portable library, i think even a Haiku port works, LOL. @tringali, I am kind of of two minds about your suggestion. of course I love the idea of reinvigorating the base and Nedit community by getting a 6.0 release out. but my only concern is that xnedit and NG are on somewhat divergent paths from a common ancestor. what happens when NG...

@efa My efforts are towards Nedit-NG which after discussions with @tringali is planned to eventually become NEdit 6.0. (Life has been busy, but we'll get there). NG has many of the features xnedit has as it is a full port to Qt. The main differentiator is that xnedit has unicode support. I am intentionally not persuing that goal until after it is ready to be called "NEdit 6.0" as the goal of NG is to be a near perfect, drop in replacement for NEdit 5.x just with a modern UI and improvements under...

Hello kangwoosukeq! So two things. You are absolutely correct, this is definitely a buffer overflow. NEdit 5.x is now considered to be "legacy" and has no planned active development going forward. The good news is that NEdit-NG https://github.com/eteran/nedit-ng/ is going to be officially considered NEdit 6.0 at some point (hopefully soon, but it's subject to the amount of time I can dedicate to it and for the past several months, I have just been absolutely swamped). NG is is in a very workable...

@Amiga Do you know if this is with Nedit6 or the classic branch?

Hi Ericxuo! So the current version in git here is a mirror of nedit-ng (https://github.com/eteran/nedit-ng), which you have actually contributed to! (Thanks :-) !) The only differences between that version and the git version here are some small patches to rebrand it as "nedit 6.0" as NG is going to be the future "main version of nedit". So the address your issues: yes, the nc executable is now named ncl, this is almost certainly a choice from Scott Tringali to avoid a conflict with the nearly ubiquitous...