The script now "copies" the tutor file to the temporary directory with a
"unique" file name, so the tutorial now lines up with the buffer state.
This one-liner already works far better than the official vimtutor.bat
ever did! It's only missing language selection, but this doesn't matter
since w64devkit discards internationalization anyway.
It would be interesting for w64devkit to be part of some sort of intro
to programming that targets Windows users who haven't yet graduated to a
more appropriate operating system. These people would need vimtutor in
order to make use of Vim.
Unfortunately the Vim developers decided that vimtutor should be a
complicated, fragile script rather than a feature built into Vim. After
a couple hours of trying, I still can't get the original vimtutor.bat
working reliably. So instead I included a one liner script that does 95%
of the job reliably. Unfortunately it's not an exact match with the
instructions, but this is the best I've found so far.
pthreads already works fine in C, so I assumed C++ threads worked.
However, it requires choosing POSIX, not Win32, threads during GCC's
configuration, which, in retrospect, makes sense.
I would have used this in the first place, but the official Mingw-w64
website still supplies the wrong download link six months after v7.0.0
was released.
This upgrade is required to work around a bug in Mingw-w64 7.0.0:
https://github.com/vim/vim/issues/4913
I would have used this version of Vim initially, but the Vim website
still lists 8.1 as the latest version five months after the release of
8.2.
Unfortunately Universal Ctags has never made an official release, and
the maintainer doesn't seem to be interesting in ever making one. So
there's no official stable tarball of the source code. GitHub's
automatically generated tarballs are not stable, so we can't use them.
So the best we can do is use a stable snapshot from a Linux
distribution, in this case Debian. This means we're limited to whatever
version Debian packages.
Trying to run in the background doesn't work because the parameter
quoting gets screwed up. As far as I can tell, the batch script language
is simply broken and there's no solution here, so don't even bother.
