I've been using the Windows command line's copy command to create empty files, but there's another easy way to do the same thing using Git for Windows.

Once you install Git in Windows, every time you're in a folder, a right-click of the mouse gives you the choices Git GUI here and Git Bash here.

If you then left-click on Git Bash here, a Linux/Unix-like terminal will open at the path of your folder, and you can use any number of Bash commands.

To create a file, use the Unix/Linux stalwart touch:

$ touch filename

This will give you a file named filename. Substitute the file name you really want.

Then close the terminal. That's all there is to it.

The Windows file manager lets you create all kinds of new, empty files as long as they either have a .txt extension or are of a Microsoft file type.

I just wanted to create empty files with no extension that I can later open in Gvim.

Basically I want the Windows equivalent of the Unix/Linux command touch.

There's a complicated Stack Overflow page on this topic, and the easiest method by far is this one that uses the Windows command line:

C:\Users\name\your\path> copy nul filename

Substitute the filename you want for filename, and you're good to go.

I've seen ways of turning this into a batch file and then somehow right-clicking to invoke it, but for now I'll just open the Windows terminal and use it that way.

I turned the laptop off and only booted once from Puppy Linux's Xenialpup over the weekend. When I turned on the laptop (2017 HP Envy) to start working in Windows 10, today, for some reason the desktop remembered that I had at least one Google Chrome tab and a few apps open.

I also started a new Chrome window for my "main" work, and the laptop was aggressively swapping for maybe a half-hour, during which time things barely worked, or were just slow as hell -- whatever you want to call it.

Now that I've been working for a couple of hours, everything is working well, but this just serves as a point of evidence that Windows 10, right when it starts up, isn't exactly ready for "vigorous computing."