Search
483 results for “zirias”
-
#dos2ansi v1.6.1 (a pure bugfix/service release):
https://github.com/Zirias/dos2ansi/releases/tag/v1.6.1* Fix possible crash (🙈) when querying for font or codepage on a file with a non-text #SAUCE type.
* Try to parse something meaningful even out of partially broken SAUCE dataYep, the possible crash was the reason to create a release even for a pretty "small" bugfix. 🙄 Chances are nobody would have noticed though, the SAUCE *display* was not affected, only the machine-readable query (-q).
Screenshot: The "offending" file. It even had literal ",1" written in the month field of the SAUCE date, but obviously meaning January here 😂
-
#dos2ansi v1.6:
https://github.com/Zirias/dos2ansi/releases/tag/v1.6* Fix cursor movement again, it never wraps or scrolls.
* Many smaller improvements to the #showansi script
* Add an example configuration using scalable fonts from https://int10h.org/oldschool-pc-fonts/ instead of the default bitmap fontsScalable fonts are a tradeoff here. You get freely configurable sizes and correction of aspect ratio. You lose pixel-perfect (perfectly sharp) display. You can't have both, unfortunately.
Screenshot shows scalable fonts 😉
-
There was still room for improvement ....
From "just needs a little #script to turn #dos2ansi in a nice ANSIart viewer" to a ~400-lines "monster" in 8 days ... 😂
It *should* work well with any #POSIX #shell. I hope so. 🙈
https://github.com/Zirias/dos2ansi/blob/master/src/bin/dos2ansi/showansi.in -
It's done, #dos2ansi v1.5 is here:
https://github.com/Zirias/dos2ansi/releases/tag/v1.5Apart from supporting all the cursor movement and screen erasing sequences that were needed for that silly file I found, there's now also support for the screen mode setting from ANSI.SYS (with non-text modes silently ignored).
There are also tons of little improvements to the "showansi" script, which should now work very well as a generic DOS ANSIart viewer picking reasonable defaults (and making it easy to override them if really necessary).
Example screenshot includes rendering this silly file again 😂
Have fun, and if you need some files to display, have a look at https://16colo.rs/
-
#make hacking can be fun too 🙈
It's hard to find something that can't be solved using nothing but some "modern" make.
Here's my #GNUmake solution for text substitutions in case you don't want to rely on #sed being available. This abuses features to turn a #Makefile more or less into a #script you can just call from a #recipe. 😏
-
I'm about to prepare yet another release, #dos2ansi v1.3.
Finding these bitmap fonts triggered two things:
1. I realized dos2ansi needs a mode to NOT attempt to mimic #VGA looks by chosing more similarly looking characters: A font recreating the orignal IBM fonts probably won't have glyphs for these other characters (and the original ones will look, well, original 😜 ...)
2. It gave me the idea that I now had everything in place for some sort of "ANSI viewer", just needs a script to tie together dos2ansi, #xterm, #less and the #ibmfonts. So, here it is: showansi. It should work with other X terminals, pagers, fonts, for configuration see the updated README:
https://github.com/Zirias/dos2ansiThe script first calls dos2ansi to query some #SAUCE metadata it then uses to pick the most appropriate font, window size and title for xterm.
The screenshot uses completely unconfigured Xorg and xterm, to show the script sets everything as needed.
-
And #pixelperfect (minus aspect ratio correction) #VGA display is possible in #xterm using bitmap(!) fonts I found here:
https://github.com/farsil/ibmfontsAs always, it wasn't *that* simple ... xterm expects a complete set of #VT100 drawing characters to be available, otherwise it will render its own which leads to funny color bugs at least with the "medium shade" used a lot in #ansiart ...
... so, let's patch the missing ones in (using dummy empty glyphs), which I did here in a #FreeBSD port for these fonts:
https://github.com/Zirias/zfbsd-ports/tree/local/x11-fonts/ibmfontsScreenshots show #dos2ansi render some ansiart and its #SAUCE info, once in VGA-9x16 and for comparison in VGA-8x16 😎
-
Released v0.6.1 just fixing one stupid little regression from refactoring: The terminfo writer must never be used when output does *not* go to stdout 🙈
So far so good, I just thought there was yet another bug, testing redirected output on #Windows. I *always* got a file encoded as #UTF16LE, no matter which format I chose (and with #UTF8 chosen, the output was just broken). Meditated on the code for a while. Looks all perfectly good.
Finally, I tested in good old #CMD. And it worked perfectly well.
So, #Powershell is messing with the encoding of my stdout stream on redirects. Really? Really??? WTF, #Microsoft? How should that ever do any good? 🤯
-
dos2ansi v0.6 released 🥳
This version brings specialized writers for direct terminal output, using #terminfo (via #curses) on non-windows and configuring the #ANSI writer for 256 colors on #Windows >= 10, otherwise using a writer for the legacy Windows Console API.
It *should* work fine on any Windows and any Unix-like system offering terminfo/curses, but I could only test on #FreeBSD and Windows Server 2022 myself, so it would be nice if someone could test on older Windows as well as other *nix systems like #Linux 😉
-
Just released dos2ansi v0.4, with lots of #DOS #codepage s supported and a testmode to display them.
The next nice feature would be to use the actual terminal capabilities if output goes there. Very simple on *nix-like systems (#Linux, #FreeBSD, ...), just link #curses and use the termcap functions.
Thinking about #Windows again, either I keep relying on #UTF8 support (since #win7 IIRC? and still a bit buggy) and #ANSI sequences support (since #win10) .... OR I attempt to use the native #Console #API there (using special functions to write in #UTF16 and other special functions to set colors, which would require a major refactoring first 🙄)
-
New pre-release of dos2ansi: v0.2
* Works on #Windows, win32 binary (cross-compiled on #FreeBSD) attached
* Selectable input #codepage (so far only #cp437, #cp850 and #cp858)
* Selectable output format, #utf8, #utf16 or #utf16le, with or without #BOMStill a few things to add, e.g. use #termcap/#terminfo or Windows Console API for "color output" when applicable ... we will see 😎
-
New pre-release of dos2ansi: v0.2
* Works on #Windows, win32 binary (cross-compiled on #FreeBSD) attached
* Selectable input #codepage (so far only #cp437, #cp850 and #cp858)
* Selectable output format, #utf8, #utf16 or #utf16le, with or without #BOMStill a few things to add, e.g. use #termcap/#terminfo or Windows Console API for "color output" when applicable ... we will see 😎
-
New pre-release of dos2ansi: v0.2
* Works on #Windows, win32 binary (cross-compiled on #FreeBSD) attached
* Selectable input #codepage (so far only #cp437, #cp850 and #cp858)
* Selectable output format, #utf8, #utf16 or #utf16le, with or without #BOMStill a few things to add, e.g. use #termcap/#terminfo or Windows Console API for "color output" when applicable ... we will see 😎
-
New pre-release of dos2ansi: v0.2
* Works on #Windows, win32 binary (cross-compiled on #FreeBSD) attached
* Selectable input #codepage (so far only #cp437, #cp850 and #cp858)
* Selectable output format, #utf8, #utf16 or #utf16le, with or without #BOMStill a few things to add, e.g. use #termcap/#terminfo or Windows Console API for "color output" when applicable ... we will see 😎
-
New pre-release of dos2ansi: v0.2
* Works on #Windows, win32 binary (cross-compiled on #FreeBSD) attached
* Selectable input #codepage (so far only #cp437, #cp850 and #cp858)
* Selectable output format, #utf8, #utf16 or #utf16le, with or without #BOMStill a few things to add, e.g. use #termcap/#terminfo or Windows Console API for "color output" when applicable ... we will see 😎
-
Update on my #FreeBSD #Linuxulator "userland from source" project: Fixing "interesting" issues 🙄
I meanwhile created a #ports #overlay, for easy testing in different environments, and trying it on my "productive" builder, there were suddenly lots of failures. The "weirdest" one now took me many days to fully understand: For some ports, "stage" seemed to install the files just fine, yet "package" didn't find any files. 🤯
Turns out installing using #Linux tools created the stagedir below /compat/linux instead. Trying to understand why, the answer was "because it could".
The indirect reason was #ccache, forcing #poudriere to do everything as root by default, and for root, /compat/linux is writable. There are still some other fails, maybe also ccache-related, but at least I just committed a workaround (including a warning) for *this* issue:
https://github.com/Zirias/freebsd-ports-overlay-linuxsrc/commit/e354a4d999e79f40d0f6aee1a40c897613ec7460 -
Did some minor fixes and overall improvements in the new USES=linuxsrc today ... it already grew quite large 🤔
https://github.com/Zirias/zfbsd-ports/blob/linux/Mk/Uses/linuxsrc.mkBTW, a while ago, I couldn't resist to add some #branding to the #FreeBSD #Linuxulator toolchain, currently in line 119.
I mean, the #vendor field in these target triplets is there for a reason, right? To be used by vendors? 😏
-
-
No. #FreeBSD provides only #termcap as standard right now. #terminfo is only available as a port.
It's possibly the only mainstream operating system where this is still the case. NetBSD and OpenBSD both provide terminfo. I haven't checked Illumos.
https://github.com/freebsd/freebsd-src/tree/main/share/termcap
-
No. #FreeBSD provides only #termcap as standard right now. #terminfo is only available as a port.
It's possibly the only mainstream operating system where this is still the case. NetBSD and OpenBSD both provide terminfo. I haven't checked Illumos.
https://github.com/freebsd/freebsd-src/tree/main/share/termcap
-
No. #FreeBSD provides only #termcap as standard right now. #terminfo is only available as a port.
It's possibly the only mainstream operating system where this is still the case. NetBSD and OpenBSD both provide terminfo. I haven't checked Illumos.
https://github.com/freebsd/freebsd-src/tree/main/share/termcap
-
No. #FreeBSD provides only #termcap as standard right now. #terminfo is only available as a port.
It's possibly the only mainstream operating system where this is still the case. NetBSD and OpenBSD both provide terminfo. I haven't checked Illumos.
https://github.com/freebsd/freebsd-src/tree/main/share/termcap
-
No. #FreeBSD provides only #termcap as standard right now. #terminfo is only available as a port.
It's possibly the only mainstream operating system where this is still the case. NetBSD and OpenBSD both provide terminfo. I haven't checked Illumos.
https://github.com/freebsd/freebsd-src/tree/main/share/termcap
-
-
-
-
