Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> we really should be devoting some chunk of it to showing what’s on the clipboard, or at least that there’s something there.

I could see that. Microsoft tried something like that with a stack-based (presumption) clipboard in Office. I don't think it worked very well. I thought it was confusing for most. You went from copy-this-and-then-paste-it to having to select what you wanted to paste. Simple is better in this case.

I can think of no instance where I explicitly needed to know what was in the clipboard. Now, admittedly, this is me, a single data point and not a casual user. I am sure it is different for casual users. In fact, I am sure that most of them don't have a clue that ctrl-c/v/x/z exist.

As for devoting screen real-estate for showing clipboard content. I can't really get a feel for the idea because I don't feel that I need it. In some cases I know that I don't want to give up any screen real-estate to anything other the the application/s currently running. For example, my EDA package uses three screens very well. I don't want to see anything else while doing this work. Again, just me.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: