#zimk β Public Fediverse posts
Live and recent posts from across the Fediverse tagged #zimk, aggregated by home.social.
-
Yet another revision, #dos2ansi v1.6.3
https://github.com/Zirias/dos2ansi/releases/tag/v1.6.3--- brings yet another subtle bugfix in #showansi: To set the title with an escape sequence, it uses "printf %b" with its \-notation for control characters, so literal backslashes in the title must be escaped as well π
Apart from that, added nice "portability bikeshed":
- Removed the dependency on 'sed' again, quoting/escaping strings for 'eval' *can* be done in pure #POSIX #shell script.
- Added proper detection of the POSIX shell to my #zimk build system, along with variables to override the choice. Used that to generate the shebang for #dos2ansi. Really an awesome way to write /bin/sh without writing /bin/sh π (rumors say there *are* POSIX systems with the compliant shell in a different path ...)
Screenshot: Yet another file with "weird" title from #SAUCE
-
A few fixes were needed to #zimk (my very own #GNU #make framework) to make everything work perfectly again in #Windows #CMD.
Testing these now, here's building #dos2ansi on Windows with just 'make' and 'mingw' installed from #chocolatey π
(building worked before as well, but there were lots of glitches and issues like e.g. partially broken "clean" rules)
-
Time to verify all my additions to my #GNUmake framework #zimk didn't break compatibility with #Windows #CMD -- they didn't π
So, you can still build #dos2ansi yourself on Windows with the minimal set of tooling installed, e.g. using #chocolatey, 'choco install mingw' and 'choco install make' is enough βοΈ
The garbled output seen in the screenshot is a consequence of Windows #Console output being strictly unbuffered, which allows these things to happen with make jobs ... I see no way to work around this .... π