data/sessions/explorer-move-to-folder-3/memory.md

Memory: explorer-move-to-folder-3

Overview

Move a file into a subfolder from a shell. Use this as the terminal route to the same end state as the file-manager move: one command names the source and the destination folder and nothing is left behind. The recorded trace opens a shell, moves report.pdf into dest\, and closes the shell with exit.

Prerequisites

• A desktop environment with a file manager, or a shell.
• A file to move and a destination folder, both existing before the task starts and both identifiable by name.
• Write access to both the source folder and the destination. A move deletes from one and creates in the other, so read access to the file alone is not enough.
• Clarity that the result is a move, not a copy. Nothing must remain at the source when the task finishes.
• No file of the same name already in the destination — it is overwritten without a useful warning, and the original is gone by then, so the overwritten data is unrecoverable.
• Both locations on the same volume, where that can be arranged. A move within a volume renames an entry; a move across volumes copies and then deletes, which takes time proportional to the file and can fail partway.

Steps

Step 1 — Left-click at (268, 1060)

The task is to move a file into a subfolder, leaving nothing behind, which is a single move command, so the first move is to open a shell. Move the cursor and Left-click the PowerShell icon in the taskbar.

Step 2 — Type: Move-Item $env:USERPROFILE\corpus-seed\report.pdf $env:USERPROFILE\corpus-seed\dest\

Type a Move-Item command naming the source file and the destination folder. Move-Item relocates rather than duplicating, so nothing is left at the source — the single-word difference from Copy-Item is the entire difference between this task and the copy task.

Step 3 — Press: Enter

After typing the command Press Enter to run the move.

Step 4 — Type: exit

Type exit to close the shell.

Step 5 — Press: Enter

After typing the exit Press Enter to run it and close the window.

Notes & Edge Cases

1. The trailing separator is what forces the destination to be a directory. Without it, a destination that does not exist is treated as a new name and the file is renamed instead of moved — the original disappears, a strangely named file appears, and nothing reports an error. It is the single most consequential character in the command.
2. The command overwrites a same-named file at the destination without asking, and the source is gone by then. Unlike a copy there is nothing left to recover from, so check the destination first or use the option that refuses to replace.
3. A move within one volume is instant; across volumes it is a copy followed by a delete. The slow case can fail partway and leave the file in both places, or in neither, so where the data matters confirm both ends rather than assuming the operation is atomic.
4. The same verb renames and moves. Which one happens depends entirely on whether the destination resolves to an existing directory, which is why the destination's existence matters more here than in most commands.
5. Absolute paths built from the environment variable keep the command independent of the shell's current directory, which is unknown in a freshly opened window.
6. The environment variable is expanded by the shell, so the same string handed to something that is not a shell leaves the literal text unresolved.
7. The prompt returning is not confirmation that the file arrived. Check the destination, and check that the source is empty.