Search
483 results for “zirias”
-
I'm planning to create a release #dos2ansi v2.0 soon, which will have more or less the feature set of v1.8, but with complete and helpful documentation for everything. Main work left to do for that is to add more text to the manpages 😉
At least, the tool I wrote for generating docs now has everything I'll need for that!
-
I'm planning to create a release #dos2ansi v2.0 soon, which will have more or less the feature set of v1.8, but with complete and helpful documentation for everything. Main work left to do for that is to add more text to the manpages 😉
At least, the tool I wrote for generating docs now has everything I'll need for that!
-
I'm planning to create a release #dos2ansi v2.0 soon, which will have more or less the feature set of v1.8, but with complete and helpful documentation for everything. Main work left to do for that is to add more text to the manpages 😉
At least, the tool I wrote for generating docs now has everything I'll need for that!
-
I'm planning to create a release #dos2ansi v2.0 soon, which will have more or less the feature set of v1.8, but with complete and helpful documentation for everything. Main work left to do for that is to add more text to the manpages 😉
At least, the tool I wrote for generating docs now has everything I'll need for that!
-
I'm planning to create a release #dos2ansi v2.0 soon, which will have more or less the feature set of v1.8, but with complete and helpful documentation for everything. Main work left to do for that is to add more text to the manpages 😉
At least, the tool I wrote for generating docs now has everything I'll need for that!
-
Here's a quick demo how the new documentation generation in #dos2ansi works 😎
https://github.com/Zirias/mkclidocScreenshots:
- Input format (on github)
- help (-h) output (on #Windows)
- manpage (on #FreeBSD)Might make sense to add some #HTML output as well, e.g. for the Windows binary package... 🤔
-
Here's a quick demo how the new documentation generation in #dos2ansi works 😎
https://github.com/Zirias/mkclidocScreenshots:
- Input format (on github)
- help (-h) output (on #Windows)
- manpage (on #FreeBSD)Might make sense to add some #HTML output as well, e.g. for the Windows binary package... 🤔
-
Here's a quick demo how the new documentation generation in #dos2ansi works 😎
https://github.com/Zirias/mkclidocScreenshots:
- Input format (on github)
- help (-h) output (on #Windows)
- manpage (on #FreeBSD)Might make sense to add some #HTML output as well, e.g. for the Windows binary package... 🤔
-
Here's a quick demo how the new documentation generation in #dos2ansi works 😎
https://github.com/Zirias/mkclidocScreenshots:
- Input format (on github)
- help (-h) output (on #Windows)
- manpage (on #FreeBSD)Might make sense to add some #HTML output as well, e.g. for the Windows binary package... 🤔
-
Here's a quick demo how the new documentation generation in #dos2ansi works 😎
https://github.com/Zirias/mkclidocScreenshots:
- Input format (on github)
- help (-h) output (on #Windows)
- manpage (on #FreeBSD)Might make sense to add some #HTML output as well, e.g. for the Windows binary package... 🤔
-
#dos2ansi v1.8 released!
https://github.com/Zirias/dos2ansi/releases/tag/v1.8There's some major rework inside adding support for seekable streams, which was necessary to implement the logic detecting #SAUCE even when the preceding DOS EOF character is missing.
Quite some improvements to the #showansi script as well, now comes with "fontsets" (explained in the comments in these and the config file) 😎
Plus added a manpage. Wanted a single source of truth (shared with the help output) and didn't find a good tool for that, so I quickly came up with my own:
https://github.com/Zirias/mkclidoc
It's bundled with dos2ansi now. Can produce man in both classic troff and BSD mandoc. The default choice is based on `uname` for now, tested on #FreeBSD and #Debian. -
#dos2ansi v1.8 released!
https://github.com/Zirias/dos2ansi/releases/tag/v1.8There's some major rework inside adding support for seekable streams, which was necessary to implement the logic detecting #SAUCE even when the preceding DOS EOF character is missing.
Quite some improvements to the #showansi script as well, now comes with "fontsets" (explained in the comments in these and the config file) 😎
Plus added a manpage. Wanted a single source of truth (shared with the help output) and didn't find a good tool for that, so I quickly came up with my own:
https://github.com/Zirias/mkclidoc
It's bundled with dos2ansi now. Can produce man in both classic troff and BSD mandoc. The default choice is based on `uname` for now, tested on #FreeBSD and #Debian. -
#dos2ansi v1.8 released!
https://github.com/Zirias/dos2ansi/releases/tag/v1.8There's some major rework inside adding support for seekable streams, which was necessary to implement the logic detecting #SAUCE even when the preceding DOS EOF character is missing.
Quite some improvements to the #showansi script as well, now comes with "fontsets" (explained in the comments in these and the config file) 😎
Plus added a manpage. Wanted a single source of truth (shared with the help output) and didn't find a good tool for that, so I quickly came up with my own:
https://github.com/Zirias/mkclidoc
It's bundled with dos2ansi now. Can produce man in both classic troff and BSD mandoc. The default choice is based on `uname` for now, tested on #FreeBSD and #Debian. -
#dos2ansi v1.8 released!
https://github.com/Zirias/dos2ansi/releases/tag/v1.8There's some major rework inside adding support for seekable streams, which was necessary to implement the logic detecting #SAUCE even when the preceding DOS EOF character is missing.
Quite some improvements to the #showansi script as well, now comes with "fontsets" (explained in the comments in these and the config file) 😎
Plus added a manpage. Wanted a single source of truth (shared with the help output) and didn't find a good tool for that, so I quickly came up with my own:
https://github.com/Zirias/mkclidoc
It's bundled with dos2ansi now. Can produce man in both classic troff and BSD mandoc. The default choice is based on `uname` for now, tested on #FreeBSD and #Debian. -
#dos2ansi v1.8 released!
https://github.com/Zirias/dos2ansi/releases/tag/v1.8There's some major rework inside adding support for seekable streams, which was necessary to implement the logic detecting #SAUCE even when the preceding DOS EOF character is missing.
Quite some improvements to the #showansi script as well, now comes with "fontsets" (explained in the comments in these and the config file) 😎
Plus added a manpage. Wanted a single source of truth (shared with the help output) and didn't find a good tool for that, so I quickly came up with my own:
https://github.com/Zirias/mkclidoc
It's bundled with dos2ansi now. Can produce man in both classic troff and BSD mandoc. The default choice is based on `uname` for now, tested on #FreeBSD and #Debian. -
I just released #dos2ansi v1.7, which includes one final bugfix: Quoted output of #SAUCE metadata should use proper "shell-style" quoting, so it can be directly consumed by #showansi, which it does now. Plus #showansi got a (tiny) bit of optimization.
https://github.com/Zirias/dos2ansi/releases/tag/v1.7
Well, just after releasing, I found more stuff to tackle. No, not new bugs at least.
But more weirdly broken ANSIart files. Example:
https://16colo.rs/pack/root0297/FU-B%26B.ANSThis one *has* SAUCE metadata, but it's not properly "hidden" behind a DOS EOF character (0x1a), which means even 'type' on a real DOS machine will output the SAUCE gibberish below the pic 🙈
So, there *might* be a v1.8 adding more heuristics to detect and parse more broken SAUCE ... 😂
-
I just released #dos2ansi v1.7, which includes one final bugfix: Quoted output of #SAUCE metadata should use proper "shell-style" quoting, so it can be directly consumed by #showansi, which it does now. Plus #showansi got a (tiny) bit of optimization.
https://github.com/Zirias/dos2ansi/releases/tag/v1.7
Well, just after releasing, I found more stuff to tackle. No, not new bugs at least.
But more weirdly broken ANSIart files. Example:
https://16colo.rs/pack/root0297/FU-B%26B.ANSThis one *has* SAUCE metadata, but it's not properly "hidden" behind a DOS EOF character (0x1a), which means even 'type' on a real DOS machine will output the SAUCE gibberish below the pic 🙈
So, there *might* be a v1.8 adding more heuristics to detect and parse more broken SAUCE ... 😂
-
I just released #dos2ansi v1.7, which includes one final bugfix: Quoted output of #SAUCE metadata should use proper "shell-style" quoting, so it can be directly consumed by #showansi, which it does now. Plus #showansi got a (tiny) bit of optimization.
https://github.com/Zirias/dos2ansi/releases/tag/v1.7
Well, just after releasing, I found more stuff to tackle. No, not new bugs at least.
But more weirdly broken ANSIart files. Example:
https://16colo.rs/pack/root0297/FU-B%26B.ANSThis one *has* SAUCE metadata, but it's not properly "hidden" behind a DOS EOF character (0x1a), which means even 'type' on a real DOS machine will output the SAUCE gibberish below the pic 🙈
So, there *might* be a v1.8 adding more heuristics to detect and parse more broken SAUCE ... 😂
-
I just released #dos2ansi v1.7, which includes one final bugfix: Quoted output of #SAUCE metadata should use proper "shell-style" quoting, so it can be directly consumed by #showansi, which it does now. Plus #showansi got a (tiny) bit of optimization.
https://github.com/Zirias/dos2ansi/releases/tag/v1.7
Well, just after releasing, I found more stuff to tackle. No, not new bugs at least.
But more weirdly broken ANSIart files. Example:
https://16colo.rs/pack/root0297/FU-B%26B.ANSThis one *has* SAUCE metadata, but it's not properly "hidden" behind a DOS EOF character (0x1a), which means even 'type' on a real DOS machine will output the SAUCE gibberish below the pic 🙈
So, there *might* be a v1.8 adding more heuristics to detect and parse more broken SAUCE ... 😂
-
I just released #dos2ansi v1.7, which includes one final bugfix: Quoted output of #SAUCE metadata should use proper "shell-style" quoting, so it can be directly consumed by #showansi, which it does now. Plus #showansi got a (tiny) bit of optimization.
https://github.com/Zirias/dos2ansi/releases/tag/v1.7
Well, just after releasing, I found more stuff to tackle. No, not new bugs at least.
But more weirdly broken ANSIart files. Example:
https://16colo.rs/pack/root0297/FU-B%26B.ANSThis one *has* SAUCE metadata, but it's not properly "hidden" behind a DOS EOF character (0x1a), which means even 'type' on a real DOS machine will output the SAUCE gibberish below the pic 🙈
So, there *might* be a v1.8 adding more heuristics to detect and parse more broken SAUCE ... 😂
-
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
-
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
-
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
-
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
-
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
-
And now there's even #dos2ansi v1.6.2: https://github.com/Zirias/dos2ansi/releases/tag/v1.6.2
The good thing is: The issues I'm fixing here are getting more and more obscure 😂
First I noticed #xterm doesn't accept all #utf8 for its '-title' option, no matter what. But it *does* support the escape sequence to set a title, so, why not use this instead.
Having added support for that (and also optionally for setting the window size using an escape sequence), I had a look at quoting again. Indeed, #showansi failed for e.g. file names containing #shell special characters.
Therefore added a *safe* quote function. The downside is, it requires #sed now. Well ....
Screenshot shows both improvements, I picked a "maximum weird" file name and used a file that has an 'ö' in its title 🥳 -- in the showansi debugging output, you can see the quoting in action 🤯
-
And now there's even #dos2ansi v1.6.2: https://github.com/Zirias/dos2ansi/releases/tag/v1.6.2
The good thing is: The issues I'm fixing here are getting more and more obscure 😂
First I noticed #xterm doesn't accept all #utf8 for its '-title' option, no matter what. But it *does* support the escape sequence to set a title, so, why not use this instead.
Having added support for that (and also optionally for setting the window size using an escape sequence), I had a look at quoting again. Indeed, #showansi failed for e.g. file names containing #shell special characters.
Therefore added a *safe* quote function. The downside is, it requires #sed now. Well ....
Screenshot shows both improvements, I picked a "maximum weird" file name and used a file that has an 'ö' in its title 🥳 -- in the showansi debugging output, you can see the quoting in action 🤯
-
And now there's even #dos2ansi v1.6.2: https://github.com/Zirias/dos2ansi/releases/tag/v1.6.2
The good thing is: The issues I'm fixing here are getting more and more obscure 😂
First I noticed #xterm doesn't accept all #utf8 for its '-title' option, no matter what. But it *does* support the escape sequence to set a title, so, why not use this instead.
Having added support for that (and also optionally for setting the window size using an escape sequence), I had a look at quoting again. Indeed, #showansi failed for e.g. file names containing #shell special characters.
Therefore added a *safe* quote function. The downside is, it requires #sed now. Well ....
Screenshot shows both improvements, I picked a "maximum weird" file name and used a file that has an 'ö' in its title 🥳 -- in the showansi debugging output, you can see the quoting in action 🤯
-
And now there's even #dos2ansi v1.6.2: https://github.com/Zirias/dos2ansi/releases/tag/v1.6.2
The good thing is: The issues I'm fixing here are getting more and more obscure 😂
First I noticed #xterm doesn't accept all #utf8 for its '-title' option, no matter what. But it *does* support the escape sequence to set a title, so, why not use this instead.
Having added support for that (and also optionally for setting the window size using an escape sequence), I had a look at quoting again. Indeed, #showansi failed for e.g. file names containing #shell special characters.
Therefore added a *safe* quote function. The downside is, it requires #sed now. Well ....
Screenshot shows both improvements, I picked a "maximum weird" file name and used a file that has an 'ö' in its title 🥳 -- in the showansi debugging output, you can see the quoting in action 🤯
-
And now there's even #dos2ansi v1.6.2: https://github.com/Zirias/dos2ansi/releases/tag/v1.6.2
The good thing is: The issues I'm fixing here are getting more and more obscure 😂
First I noticed #xterm doesn't accept all #utf8 for its '-title' option, no matter what. But it *does* support the escape sequence to set a title, so, why not use this instead.
Having added support for that (and also optionally for setting the window size using an escape sequence), I had a look at quoting again. Indeed, #showansi failed for e.g. file names containing #shell special characters.
Therefore added a *safe* quote function. The downside is, it requires #sed now. Well ....
Screenshot shows both improvements, I picked a "maximum weird" file name and used a file that has an 'ö' in its title 🥳 -- in the showansi debugging output, you can see the quoting in action 🤯