data/sessions/finder-duplicate-file/memory.md

Memory: finder-duplicate-file

Overview

Duplicate a file in place through the file manager's context menu. Use this when a second copy of a file is wanted in the same folder and the file is being worked with by pointing rather than by name. The route right-clicks the file — which selects it and opens its menu in one action — and chooses Duplicate. The recorded trace leaves report copy.pdf beside report.pdf, byte-identical in size to the original.

Prerequisites

• A desktop environment with a file manager, or a shell — either route reaches the same end state.
• A file that already exists and can be identified at run time, together with the folder holding it. The file is found by name, so the name has to be known; its path does not.
• Write access to that folder. The copy is created beside the original, so the folder itself must be writable even though the original is only read.
• Enough free space for a second copy of the file.
• A decision about the copy's name. The file manager names it automatically, following its own convention; a shell names it explicitly. The two produce the same file only if the shell is told to use the same name.
• No file already occupying the copy's name. The shell route overwrites it silently; the file manager route sidesteps it by choosing a different name, which is a different end state from the one intended.

Steps

Step 1 — Move-cursor at (433, 360)

The task is to make a second copy of report.pdf in the folder it already sits in, so the file has to be selected before any command can act on it. Move the cursor onto the report.pdf icon in the second row of the corpus-seed window. Moving to the target and clicking as a separate step is more dependable than a combined move-and-click, which sometimes reaches the position without the click registering.

Step 2 — Right-click at (433, 360)

Move the cursor and Right-click report.pdf to select it and open its context menu in one action. The menu holds Duplicate, which is the file-manager operation that makes a copy in place; reaching for it through the context menu means the file is named by pointing at it rather than by typing a path.

Step 3 — Move-cursor at (477, 524)

Before committing to a menu item, check that the menu is acting on the intended file: it reads Compress "report.pdf", which names the target explicitly, and report.pdf's label is highlighted. A context menu opened on empty space or on a neighbouring icon offers a different set of items entirely. Move the cursor down onto Duplicate.

Step 4 — Left-click at (477, 524)

Move the cursor and Left-click Duplicate. Finder copies the file into the same folder and names the copy by inserting copy before the extension, producing report copy.pdf — the name is chosen by Finder, not typed, so no dialog appears and nothing needs confirming. The new file is created selected, which is the signal that the duplication ran.

Notes & Edge Cases

1. Right-click the file itself rather than empty space. The menu that opens depends on what is under the pointer, and the duplicate command exists only on a file's own menu — empty space gives the folder's menu, which does not contain it.
2. Move to the target and click as separate actions. A combined move-and-click sometimes reaches the position without the click registering, and on a context menu that failure looks identical to the menu simply not opening.
3. The copy's name is the file manager's choice, not the task's. It appends its own word to the stem and keeps the extension, so a shell asked to do the same job has to be told that exact name — it will not invent the same one.
4. The selection moves to the new copy. That is a useful confirmation, and a trap for any keystroke issued immediately afterwards, which will act on the copy rather than on the original.
5. There is no confirmation, no progress and no undo prompt. Read which file is highlighted before invoking the command, because nothing will ask afterwards.
6. Running the task a second time does not repeat it. With a copy already present the command duplicates whatever is selected and produces a third name, so re-running is not the same as being idempotent.
7. A key command exists for this as well as the menu route. Prefer the key command when the right one is known, and fall back to menu navigation when it does not respond.
8. The file and folder names here are for demonstration. The real names, paths and locations vary by system, so verify them against the machine the task is running on rather than reusing what the trace shows.