Ghost Cut – or why Cut and Paste is broken everywhere
A developer argues that the ubiquitous 'Cut & Paste' functionality is fundamentally broken across all software, citing issues with undo, document reflow, and atomicity. They propose 'Ghost Cut' as a solution that keeps selected text visible but inert until pasted, making the operation a single atomic move. The Hacker News community largely pushed back, defending existing C&P behaviors as intentional design choices, while acknowledging the complex nature of system-wide clipboards.
The Lowdown
The author contends that the universally accepted 'Cut & Paste' (C&P) mechanism is flawed in its core implementation across text editors, code editors, and browsers. This assertion challenges decades of user interface norms and proposes a radical alternative.
- Undo Limitations: A standard 'cut' operation removes text but alters the system clipboard. While an undo restores the document, the clipboard's state remains changed, preventing a full, clean reversal of the
Ctrl-Xaction. - Reflow Disorientation: Immediately upon cutting, the document reflows. This forces users to relocate their desired paste point, adding a small but unnecessary cognitive burden to what is conceptually a text-moving operation.
- Non-Atomic Operation: Despite being perceived as a single text movement, C&P is not atomic. Undoing a paste only removes the newly inserted text, requiring a separate undo to restore the original document state, especially if intermediate edits occurred.
The proposed solution, 'Ghost Cut,' modifies the Ctrl-X action: the selected text fades and becomes inert but remains in place and is not sent to the clipboard. Pressing Escape cancels this 'ghosted' state. The Ctrl-V paste command then removes the ghosted text from its original position and inserts it, creating a single, atomic 'move' operation without involving the clipboard. The author notes that traditional 'cut-to-clipboard-and-delete' semantics would become a two-step Ctrl-C then Backspace operation, a trade-off they deem acceptable given its rare use. While acknowledging some similar functionality in applications like Excel, the author hopes for widespread adoption, even in code editors where reflow issues are less prominent.
The Gossip
Conventional Cut's Credibility
Many commenters vehemently disagreed with the premise that standard Cut & Paste is 'broken,' arguing that the author's identified 'flaws' are, in fact, intentional design choices. Users highlighted that the current behavior—where cut places text on the clipboard but document changes are undoable—is often desirable, allowing them to use cut-then-undo as a quick way to copy text to the clipboard without altering the source document. They emphasized that 'undo' is generally understood as applying to file content, not to the ephemeral state of the system-wide clipboard.
Ghost Cut's Gripes and Gains
Discussion around 'Ghost Cut' explored its practical implications and comparisons to other systems. Some acknowledged the novelty but raised concerns, particularly regarding the potential for disorientation when text reflows at the paste location rather than the cut location. Others pointed out existing parallels, such as Windows Explorer's file cut behavior or older systems like Xerox Star's 'move to' operations, suggesting drag-and-drop as a similar, underutilized alternative. The point was made that 'Ghost Cut' also introduces an intermediate state, making its 'atomicity' claim debatable, and that some find Excel's similar behavior undesirable.
Clipboard Conundrums and Cross-App Complications
A significant portion of the debate centered on the nature of the clipboard as a shared, system-wide resource versus an application-local undo stack. Commenters highlighted the inherent complexity of trying to 'undo' clipboard changes when other applications might have modified it in the interim. Many concluded that while a system-wide, undoable clipboard might be a 'cooler' solution, it would require fundamental operating system support and a level of complexity most users don't need, making app-specific 'fixes' or relying on dedicated clipboard managers a more pragmatic approach for power users.