4 ms·
I feel like this is more an indictment of the absolute mental behavior of the windows move command.
by Aeolun 1y ago
I feel like this is more an indictment of the absolute mental behavior of the windows move command.
- rbanffy 1y agoMy thoughts exactly. If the last name in the arguments is not a directory, what the hell is it even doing? It’s like a destructive `cat` command, which doesn’t exist in Unix because it would make no sense.
- llm_nerd 1y agoFWIW, 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.
- layer8 1y agoThe blog post is inaccurate about the actual behavior of the move command. When trying to move multiple files and the destination does not exist, move aborts with "Cannot move multiple files to a single file." By default, move also prompts before overwriting files. However, it doesn’t do so when invoked from a batch file, which maybe the AI agent was using.