Thorsten Haude wrote: > It sure is, that's why I wondered why you would bring these things up. > I don't mind if additional bugs are closed before the release, but we > should focus on the release-criticals.
[ 1065303 ] screen refreshment error -> priority 9 [ 1717911 ] cursor not erased completely -> priority 5 In both cases I read something like "select something and hit backspace then the cursor isn't erased completely"[1]. So, we should focus on the priority 9 one and be questioned when mentioning the other one? > >> >#1628593 Unnecessary window grow when opening file > >> > > >> > annoying for line number users > >> > fix submitted - not in cvs > >> > >> Yeah, it's kind of nasty and I got distracted while looking it over. > > > >I have applied it for testing. I got compiler warnings about const in > >static int updateGutterWidth(const WindowInfo* window) and > >static int updateLineNumDisp(const WindowInfo* window) > > That's my const, and it's more documentation than of real value. I > wonder about the warnings though, what compiler do you use and at what > -W level? gcc with default -W level (ie, don't given on command line), but I thought Bert submitted the patch. Anyway, it's pretty clear if one tells the compiler a variable would be const and then uses it as non-const the compiler informs you that const was discarded, unless one turns warnings off completely. Jörg [1] #1717911 has a fix attempt attached, btw. -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
