Re: We should release sometime...

Richard Levitte <[email protected]>
Newsgroups gmane.comp.window-managers.ctwm
Message-ID <[email protected]>
... and diff attached.  I hope that's an ok way to share small fixes,
still.

Cheers,
Richard

In message <[email protected]> on Mon, 20 Aug 2018 06:45:54 +0200 (CEST), Richard Levitte <[email protected]> said:

richard> 
richard> Explanation found...  it seems that the build is locale sensitive.  I
richard> run in a Swedish locale, where 'v' and 'w' occupy the same place in
richard> the alphabet, so this is what the end of my funckeytable looks like:
richard> 
richard>     	{ "f.unsqueeze",            FKEYWORD, F_UNSQUEEZE },
richard>     	{ "f.upiconmgr",            FKEYWORD, F_UPICONMGR },
richard>     	{ "f.upworkspace",          FKEYWORD, F_UPWORKSPACE },
richard>     	{ "f.vanish",               FKEYWORD, F_VANISH },
richard>     	{ "f.warphere",            FSKEYWORD, F_WARPHERE },
richard>     	{ "f.warpring",            FSKEYWORD, F_WARPRING },
richard>     	{ "f.warpto",              FSKEYWORD, F_WARPTO },
richard>     	{ "f.warptoiconmgr",       FSKEYWORD, F_WARPTOICONMGR },
richard>     	{ "f.warptoscreen",        FSKEYWORD, F_WARPTOSCREEN },
richard>     	{ "f.version",              FKEYWORD, F_VERSION },
richard>     	{ "f.winrefresh",           FKEYWORD, F_WINREFRESH },
richard>     	{ "f.vlzoom",               FKEYWORD, F_LEFTZOOM }, // -> f.leftzoom
richard>     	{ "f.vrzoom",               FKEYWORD, F_RIGHTZOOM }, // -> f.rightzoom
richard>     	{ "f.zoom",                 FKEYWORD, F_ZOOM },
richard>     };
richard> 
richard> Of course, that also screws up finding some of these functions, giving
richard> me some false errors in my .ctwmrc:
richard> 
richard>     ctwm:  line 447:  ignoring unknown keyword:  f.winrefresh
richard>     ctwm:  line 448:  error in input file:  syntax error
richard>     ctwm:  line 449:  ignoring unknown keyword:  f.version
richard>     ctwm:  line 509:  ignoring unknown keyword:  f.winrefresh
richard>     ctwm:  line 510:  error in input file:  syntax error
richard>     ctwm:  line 529:  ignoring unknown keyword:  f.winrefresh
richard>     ctwm:  line 530:  error in input file:  syntax error
richard>     ctwm:  errors found in twm file "/home/levitte/.ctwmrc"
richard> 
richard> Cheers,
richard> Richard
richard> 
richard> In message <[email protected]> on Mon, 20 Aug 2018 06:33:11 +0200 (CEST), Richard Levitte <[email protected]> said:
richard> 
richard> richard> 
richard> richard> Boy, have I kept away for a while!
richard> richard> 
richard> richard> Just a quick note, after a build from a fresh trunc:
richard> richard> 
richard> richard>     : ; ctwm -version
richard> richard>     ctwm: INTERNAL ERROR: funckeytable sorting: 'f.warptoscreen' >= 'f.version'
richard> richard>     ctwm: INTERNAL ERROR: funckeytable sorting: 'f.winrefresh' >= 'f.vlzoom'
richard> richard>     ctwm 4.0.2-pre
richard> richard>      (bzr:[email protected])
richard> richard> 
richard> richard> Cheers,
richard> richard> Richard
richard> richard> 
richard> richard> In message <[email protected]> on Sun, 19 Aug 2018 20:33:23 -0500, "Matthew D. Fuller" <[email protected]> said:
richard> richard> 
richard> richard> fullermd> 
richard> richard> fullermd> We've accumulated up a fair number of minor bugfixes and tweaks since
richard> richard> fullermd> 4.0.1, so I'd like to get a 4.0.2 out the door with 'em.
richard> richard> fullermd> 
richard> richard> fullermd> I've cut a snapshot tarball of the current head (r620) to make it
richard> richard> fullermd> easier to test for people not used to running out of VCS, available at
richard> richard> fullermd> <https://www.ctwm.org/tmp/ctwm-4.0.2-pre.20180819.tar.xz>
richard> richard> fullermd> 
richard> richard> fullermd>   SHA256 (ctwm-4.0.2-pre.20180819.tar.xz) =
richard> richard> fullermd>     07c015cb44634510231c82748a50d8becb0e60627421004a4cc21651990000d8
richard> richard> fullermd> 
richard> richard> fullermd> Changes can be seen in CHANGES file in the tarball, or online at
richard> richard> fullermd> <https://bazaar.launchpad.net/~ctwm/ctwm/trunk/view/head:/CHANGES.md>.
richard> richard> fullermd> They include several fixes for edge-case crashes (mostly involving
richard> richard> fullermd> multi-Screen setups), various focus-handling fixes, the just-landed
richard> richard> fullermd> naming changes, and a few other minor tweaks.  I've been consistently
richard> richard> fullermd> running the head (and often not-yet-head) on several systems without
richard> richard> fullermd> problems, so it's at least moderately stable.
richard> richard> fullermd> 
richard> richard> fullermd> 
richard> richard> fullermd> Got some spare minutes and a hankering to help de-bleed the edge?
richard> richard> fullermd> Give it a whirl, from snap or VCS!  I'd like to go ahead and make a
richard> richard> fullermd> release out of things in a week or so unless a surprise turns up.
richard> richard> fullermd> Then we can start doing bigger and riskier things toward a bigger and
richard> richard> fullermd> riskier 4.1.  High on the list; Max's RANDR changes.
richard> richard> fullermd> 
richard> richard> fullermd> 
richard> richard> fullermd> -- 
richard> richard> fullermd> Matthew Fuller     (MF4839)   |  [email protected]
richard> richard> fullermd> Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
richard> richard> fullermd>            On the Internet, nobody can hear you scream.
richard> richard> fullermd> 
richard> richard> 
richard>
mk_function_bits.sh.diff (text/x-patch, 450 B)
=== modified file 'tools/mk_function_bits.sh'
--- tools/mk_function_bits.sh	2016-11-02 07:05:18 +0000
+++ tools/mk_function_bits.sh	2018-08-20 04:53:22 +0000
@@ -17,6 +17,11 @@
 	exit 1
 fi
 
+# Make sure that the locale won't disturb the sorting
+LANG=C
+LANGUAGE=C
+LC_ALL=C
+export LANG LANGUAGE LC_ALL
 
 # We need an awk(1) that supports toupper().  Which is to say, any awk
 # less than 30 years old.  Which means 'awk' on every system on the
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.