From: Charles W. <cwi...@us...> - 2012-09-09 19:52:08
|
On 9/9/2012 3:10 PM, Thomas Dickey wrote: > There's more than one aspect: > > a) console2 hasn't been updated for about two years, and that was > a development snapshot (equivalent to my weekly patches for > ncurses). Its last stable release was 7 years ago. Based on that, > it's rather unlikely that there will be any relevant fixes by its > developers. Don't confuse *our* most recent package with *their* most recent package. They have b148 which was released...last October, so 11 months ago. We are currently advertising b147, which is, yes, two years old. I should probably bump our package, huh? However, your point is still well-taken: there have not been any git commits since that release last October. Development seems very bursty: nothing for a year, then Bang! a new release committed to git and published immediately. No telling when the next burst will occur. There are a bunch of open bugs, a bunch of open support requests -- but the project is not completely dead as /somebody/ has marked some recent bugs as invalid or closed. If ncurses won't work in console2 -- BUT we can advertise a console-handle-based [1] console replacement in which it DOES work -- then all is well. I'd be especially impressed if ncurses-win32 ALSO works in msys-mintty, but I rather doubt that (unless it has a fallback to AVOID WriteConsoleOutput[A,W] when stdin/stdout are NOT console handles). It appears that conemu MAY be a way forward, but obviously there are some code bugs and packaging kinks to work out first. [1] as opposed to cygwin-like pseudotty's, which are used by rxvt (blech, puke) and mintty. -- Chuck |