Earlier quoted context omitted.
> You can cut from app A, switch to app B, cut something else from app B, then go back to app A and undo the cut. ...right, thanks. So you could still make it work but you'd definitely need OS support, it's not something one app can fix. Edit: You could make this work on an app level by checking if the contents of the user's clipboard is still the value they cut. If yes, revert to whatever clipboard contents you save…
What would be in the clipboard after the undo in that scenario? edit: Yeah, the problem is that the user does not expect undo to do something different depending on what they did on a different program. Undo doing nothing to the clipboard always is more consistent and the better UX.
Ghost Cut – Or why Cut and Paste is broken everywhere
51–60 of 162 posts
Re: Ghost Cut – Or why Cut and Paste is broken everywhere
#52The deeper underlying problem is that we treat arbitrary UI/UX implementations as objective truth. There is one decided way your computer can be interacted with, and you the user must accommodate it. This is what I want to change.
Re: Ghost Cut – Or why Cut and Paste is broken everywhere
#53Earlier quoted context omitted.
It's really natural! - make a bunch of edits - decide I don't like all of them - copy the part I want to keep - undo a bunch - paste the good part This is copy, not cut, but it wouldn't work if the clipboard state was part of the undo system.
The article isn't arguing that clipboard state should be part of the undo system, it is arguing that cut shouldn't touch clipboard state. In the "Side effects" section they mention if you want the contents to go to the clipboard, then you should use copy instead of cut.
Re: Ghost Cut – Or why Cut and Paste is broken everywhere
#54Agree accidentally clobbering the clipboard is super annoying. Clipboard history apps are a godsend. Like Paste on Mac, or Windows has it built in.
The Mac now has a clipboard history as well, it's just a bit awkward. You can open Spotlight with ⌘Space, and within Spotlight open the clipboard manager with ⌘4.
Re: Ghost Cut – Or why Cut and Paste is broken everywhere
#55Earlier quoted context omitted.
I often cut + undo because seeing the cut is feedback which tells me the operation successfully put the content into clipboard. This is not always a guarantee especially in web apps, and sometimes I just have focus on the wrong window.
Have you used a clipboard manager? There are tons that you can configure with notifications and indicators, so you don't have to that.
Re: Ghost Cut – Or why Cut and Paste is broken everywhere
#56Re: Ghost Cut – Or why Cut and Paste is broken everywhere
#57Cut and Paste is three operations. Cut is two operations copy and delete, copy is never undone by undo it should not be undone when you cut either. I cut, undo, ..., undo, and paste multiple times a day. It's a feature not a bug. > Cut & Paste is not atomic Yes because it's two different actions. What does "Ghost Cut" do if you paste multiple times? Paste the cut text first and then what? The previous thing in your c…
> I cut, undo, ..., undo, and paste multiple times a day. Why would you cut + undo as opposed to just copy? Are they not the same operation at that point?
Re: Ghost Cut – Or why Cut and Paste is broken everywhere
#58Earlier quoted context omitted.
> I cut, undo, ..., undo, and paste multiple times a day. Why would you cut + undo as opposed to just copy? Are they not the same operation at that point?
I often cut + undo because seeing the cut is feedback which tells me the operation successfully put the content into clipboard. This is not always a guarantee especially in web apps, and sometimes I just have focus on the wrong window.
Re: Ghost Cut – Or why Cut and Paste is broken everywhere
#59Re: Ghost Cut – Or why Cut and Paste is broken everywhere
#60Agree accidentally clobbering the clipboard is super annoying. Clipboard history apps are a godsend. Like Paste on Mac, or Windows has it built in.
I first encountered clipboard history in Jetbrains Rubymine editor