Activity for Evan Teran
-
Evan Teran modified a comment on ticket #135
@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...
-
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...
-
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...
-
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! 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 utility...
-
You got it. I'll take a look at it sometime soon. Though I will probably reach out to you when it is close to ready to confirm that it works as intended since tags aren't a feature that I am a heavy user of :-)
-
@tksoh My hope is that you'll be able to use a std::stack to make it MUCH easier ;-)
-
@tksoh That's exactly what I was thinking. Since it's a port of your patch efforts, you can take the lead on this effort if you like. I'll be more than happy to help though, especially regarding how the Qt code factors in if you need it.
-
Thanks for your support! It's actually not a huge feature to add motif support. I'd be borrowing like 90% of the code from the Trolltech team's efforts ;-). But... it's certainly low priority as well since as you said, most users seem to prefer more modern looks. So, it may work its way in there, but I'm in no rush to make it happen. It may end up being more of an easter egg kinda feature :-P.
-
@tksok nice! it sounds like it works perfectly as one would expect. So regarding GUI/minimalist. My personal opinion is that it's ok to introduce new features with minimalist GUIs because we can always add a nice GUI for the feature after it's in. I definitely think this feature would make a nice addition to NG.
-
@tksoh part of the "plan" that Scott and I have discussed is to basically rebrand nedit-ng as "nedit 6.0" (My intention is to do one last release as nedit-ng very soon since I there has been a lot of small fixes since the last one, and then officially pivot to nedit-6.0) So at the very least, having the releases mirrored here may be the best way to maintain version continuity with users and distro packagers. From an ubuntu package point of view, they may just say "oh, there's a new version upstream...
-
@Akshay Chavan I am looking into using code from here to give nedit-ng an OPTIONAL classic motif look: https://github.com/qt/qtstyleplugins/blob/master/src/plugins/styles/motif/qmotifstyle.cpp It isn't perfect yet, and in particular has some bugs regarding icon menus, but it's pretty close and can serve as a good baseline.
-
@lebert can you explain how you made this branch git wise? Do you think it's even possible to adjust for example, my upstream git to have a similar "full history"? Are you basically forking nedit, and then just applying all my changes on top of it?
-
@tksoh I am intrigued by this patch, and think it is a good candidate for porting to nedit-ng, but have a few questions :-). you said that unlike bookmarks, it is "cross-window", I assume that means that it will activate the appropriate window if you moved away since? Bookmarks have a mechanism to seemlessly move the bookmark if the text is edited after the bookmark is made. For example if your text buffer just has "Hello world" and you bookmark position 6, it points to the start of "world". if you...
-
@tksoh I am intrigued by this patch, and think it is a goodcandidate for porting to nedit-ng, but have a few questions :-). you said that unlike bookmarks, it is "cross-window", I assume that means that it will activate the appropriate window if you moved away since? Bookmarks have a mechanism to seemlessly move the bookmark if the text is edited after the bookmark is made. For example if your text buffer just has "Hello world" and you bookmark position 6, it points to the start of "world". if you...
-
You raise some good points. I'm sure that Scott and I can figure out some satisfactory fix. One thing to note, is that the current plan is for my github repo to be the "main" repository going forward and for sourceforge to be synced up for releases. So my work will continue to have its git history going forward, it will just be located there. Also, yes, it was based on NEdit 5.6 sources. Evan
-
@tksoh Qt used to have a built-in Motif theme, but I think they dropped that with Qt5 :-P
-
Hey guys. I just wanted to say how excited I am to work on this with you guys. The Qt port of NEdit has been a passion project of mine for a while now and I am really looking forward to working with the larger nedit community! I'm sure that my port isn't perfect, so please do submit issues as you find them and will do my best to get it all fixed up! @tksoh has already been great in this regard! Evan
-
Yea, the nedit.rc would cover all of the styles. So yea, it would be helpful for sure. Though hopefully others who have changed more than just a couple of colors would be willing to help too :-)
-
Yea, the setup of syntax highlighting colors. Or what NEdit refers to as "Text Drawing Styles". As a whole, I am refering to the entire set of text drawing styles as a "Scheme" or "Theme".
-
Hey guys, I'm the author of nedit-ng. I am considering the idea of supporting multiple color schemes in a future release (or at least having first class support for editing the current color scheme in the UI) and while I could make some alternative color schemes myself, I'm not exactly an artist and I'm also not an expert on EVERY language that nedit supports out of the box with its default language modes. So, I was curious if any of the nedit user base have developed color schemes that they like...
-
Awesome to hear :-). My code base is quite a large change from classic nedit, but at least the concepts remain the same. As for unicode, I REALLY want to have it supported, but I do wonder how certain things should be handled: I assume internally you convert everything to UTF-8? that in itself would be the simplest place for me to start. Do some BOM detection (or let user pick), then just convert to common representation. I suspect xnedit still has the same regex engine untouched, so find/replace/syntax/etc...
-
@Pyrphoros Wow, great work! I don't know if you had seen it, but I also have a "fork" of nedit (called nedit-ng) at https://github.com/eteran/nedit-ng. I went in a different direction of porting to modern C++ with Qt. I hadn't gotten around to adding unicode support yet to mine, so I may end up taking some inspiration from your code :-). I look forward to the two of us breathing life into this editor even if we go in diverging directions. And who knows, maybe we can find a way to collaborate som...
-
@Scott, Qt did offer a lot of outright replacements for some of nedit's code, and I think at this point just about every line of code has been "touched". But there is still a lot that remains the same, at least algorithmically. @TK, No pre-built binaries, but yes, it does build on windows! There are some minor quirks such as Ctrl+Shift+0 being trapped by windows, so "shigt right by tabs" doesn't work out of the box as a keybaord shortcut. But eventually I'll add the ability to remap-shortcuts, and...
-
Hello fellow nedit lovers! I wanted to share a long running effort with the nedit community. I have been a loyal nedit user since around 2000, but unfortunately with things like 4K screens and anti-aliased fonts... it hasn't aged too well. So about a year ago I started a personal project to port nedit to Qt5 using C++14 as the underlying implemtentation language. And am finally at an "RC1" stage of development. I understand that this is a "competetor" to the traditional nedit, and in no way intend...
1
