| |||||||||||||
GNOME 3.10 ReleasedGNOME 3.10 ReleasedPosted Sep 27, 2013 14:11 UTC (Fri) by khim (subscriber, #9252)In reply to: GNOME 3.10 Released by alankila Parent article: GNOME 3.10 Released
It's just that when the address bar already has text, your click may be mistaken as a selection if the pointing device simultaneously moves slightly. “Slightly”? You must move it all the way out of address bar! If you try move you pointer with middle button clicked it'll be just ignored (mouse cursor is frozen when that happens). Just middle-click again — and you are golden! The ease of accidentally overriding the selection seems like a fundamental limitation of the select+middleclick technique. All such problems in my experience come from keyboards/mices which don't have a middle button and where you can accidentally generate left click or right click instead of middle click. What really kills me that on Linux, ctrl-C has dual purpose, the other usage is to send INT to process, and the other is to perform a copy operation. Yup. And that is why I use trackpoint in combination with middle click. Works fine in most cases (except crazy Java programs, but they are not Linux programs, they tend to try to invent their own way of doing everything anyway).
(Log in to post comments)
GNOME 3.10 Released Posted Sep 27, 2013 15:57 UTC (Fri) by apoelstra (subscriber, #75205) [Link]
<blockquote>“Slightly”? You must move it all the way out of address bar! If you try move you pointer with middle button clicked it'll be just ignored (mouse cursor is frozen when that happens). Just middle-click again — and you are golden!</blockquote>
The problem is not accidentally selecting while middle-clicking, but accidentally selecting while clicking normally. For example, you might click the address bar, hold down backspace to clear it (itself very irritating, as the more natural "triple-click and hit delete" idiom will also blow out your copy/paste buffer), then middle-click in the blank address bar.
I think, this is why Firefox treats middle-clicking in the middle of the page as a "go to URL" signal. IMHO this convenience is not really worth the suprise of Firefox jumping pages every time you miss a text box. (Pentadactyl and vimperator users can just hit 'p' or 'P' to the same effect, which is harder to do by accident.)
A more common problem, for me anyway, is that I have a habit of (a) selecting text while reading long pages as a way of bookmarking my position while scrolling or checking other windows, and (b) selecting text to delete/overwrite it. It is frustrating that both these activities lose data from the paste buffer, especially when trying to overwrite text from the clipboard.
I love middle-click-to-copy, but it could certainly be improved. Maybe if you had to use the right mouse button while dragging to copy text, that would avoid these conflicts and also prevent users who are unaware of it from accidentally using it.
GNOME 3.10 Released Posted Oct 2, 2013 12:40 UTC (Wed) by Arker (guest, #14205) [Link]
"The problem is not accidentally selecting while middle-clicking, but accidentally selecting while clicking normally. For example, you might click the address bar, hold down backspace to clear it (itself very irritating, as the more natural "triple-click and hit delete" idiom will also blow out your copy/paste buffer), then middle-click in the blank address bar."
You are attempting to use this like a two-step copy paste and it just isnt. So forget about your copy/paste buffer, that isnt even involved in the yank. You have to clear the space before you start, since there is one step, not two, it is not possible to insert a step between the steps, when there is only one step.
"A more common problem, for me anyway, is that I have a habit of (a) selecting text while reading long pages as a way of bookmarking my position while scrolling or checking other windows, and (b) selecting text to delete/overwrite it. It is frustrating that both these activities lose data from the paste buffer, especially when trying to overwrite text from the clipboard."
But they dont. The paste buffer is unaffected. You access it with shift-insert or ctrl-v or meta-v or whatever you have that mapped to - the middle shift yank uses the primary selection, NOT the paste buffer!
|
|||||||||||||