Live data from Hacker News

Ghost Cut – Or why Cut and Paste is broken everywhere

ishmael.textualize.io

161–162 of 162 posts

Re: Ghost Cut – Or why Cut and Paste is broken everywhere

#161
post #160
post #149

Earlier quoted context omitted.

> Undo should always mean: restore the state of the world (/of the system) to where it was before. So if you copy and undo you want clipboard restored instead of undoing the previous app action??? Or should it maybe undo the mouse movement? Or text cursor movement? "State of the world" was the cursor in a different place after all Such "absolutist" approach won't help you design a good system as that "always" depends…

Well, in fact a good principle is to limit side effects as much as possible. Copy or cut inside the same document should probably not involve the system clipboard at all. The system clipboard could be triggered/populated when the app goes out of focus for example.

Maybe internal registers are the primary way, though that prevents some niche cases like clipboard watchers (copied #hex color to clipboard, have an option to insert any other format).

Re: Ghost Cut – Or why Cut and Paste is broken everywhere

#162

Earlier quoted context omitted.

No. The file disappearing is something. If you cut, and don't paste, nothing happens. And there is nothing to undo.

So the "cut" file doesn't disappear from its directory when you "cut" it? Only when it's pasted?

Yes. That is what happens.
Post reply on HN