Ron Yorston

Yes, if something isn't enabled in the default configuration it's probably because it doesn't work. BusyBox uses various features from Unix, Linux and POSIX which aren't available in Microsoft Windows....

I assume the space in ```* .xls``` is a typo and you mean ```*.xls```. Since busybox-w32 version FRP-3532-g01a256149 Windows wildcards are supported by default. What you're seeing here is a...

I've added some infrastructure to make it possible to build `stty` (and the non-standard `ttysize` applet). This is in the stty branch. Since Windows consoles are quite different from ttys...

The problem with changing the console size seems to have been fixed in the Windows 10 Anniversary Update.

No, not obsolete. What errors are you getting? I don't see any problem building on Fedora 24 (gcc 6.1) or Fedora 23 (gcc 5.2).

Maybe this should go to upstream BusyBox, it doesn't seem to be WIN32-specific.

This is odd. I tried to reproduce the issue but only got the font to change once. I had a fresh installation of Windows 10 in which I hadn't run...

Not directly related to fonts, but busybox-w32 does change the code page from 850 to 858. Is that happening in your case? If so, does resetting the code page back...

It is the code page and it looks like a bug in PowerShell. If the font is Consolas 16 and the code page is changed to 858 (```chcp 858```) running...

As to *why* busybox-w32 changes code page 850 to 858, see issue #135.