FWIW, move in powershell is logical and has none of these problems. The classic move command, however, is basically DOS 3.x level.
The point being that Microsoft is trying to solve these problems, and in a normal terminal session you have all of the vastly improved command shell alternatives.
Though I still wouldn't be running anything like this on Windows proper. In WSL2, sure, it works great. Not in the base Windows with its oddball, archaic APIs and limitations.
The point being that Microsoft is trying to solve these problems, and in a normal terminal session you have all of the vastly improved command shell alternatives.
Though I still wouldn't be running anything like this on Windows proper. In WSL2, sure, it works great. Not in the base Windows with its oddball, archaic APIs and limitations.