Ryan Mast

Current status of running tests: - I can start Chrome on Linux and macOS - When starting Chrome not-headless on macOS, it pops up a "first run" dialog asking if...

@AlexRMU the rough steps I followed were: 1. Install [WinFsp](https://github.com/billziss-gh/winfsp/releases) 2. Install mingw-w64 (if not already installed, make sure it has a working copy of gcc). 3. In a MinGW...

I think the one I have on my system is listed as `MingW-W64-builds` on that page, but I don't see why Win-Builds wouldn't work to compile tabfs. Will be interesting...

Try adding the suggested option to the gcc command. Is that using the Win-Builds gcc?

Did you try adding one of the standard options the error message suggested? ``` D:\Desktop\TabFS-win-tabfs\fs\tabfs.c: In function 'tabfs_readdir': D:\Desktop\TabFS-win-tabfs\fs\tabfs.c:367:5: error: 'for' loop initial declarations are only allowed in C99 mode...

Depending on if you open it in a MinGW, MSYS, or Windows Command Prompt shell the result may vary slightly, but none of them seem to mount it correctly. From...

I don't have cygwin installed at the moment -- I'll probably have some time to test it early August, and maybe also finish the CI builds.

I think it would be preferable not to depend on Cygwin. WSL doesn't support fuse but it looks like winfuse/winfsp may have WSL support -- so that could be easier...

Digging around some, it looks like `imagebuildah/executor.go` in buildah is where an unusedArgs variable keeps track of the --build-arg options that haven't been consumed yet, and then it goes through...

No, it doesn't go away -- a cursory search for refs to unusedArgs in buildah didn't turn up anything that looked like it would be affected by the format either.