Description of problem:
Placing the RMB _within a document_, I can only cut or paste from the
Gedit menu, NOT with the mouse. undo, and redo function with the
mouse within the document.
Version-Release number of selected component (if applicable):
]$ rpm -q gedit
Steps to Reproduce:
1. Open a document from Gnome with Gedit, or open Gedit and select a new document
2. Highlight text to be cut or pasted with the right mouse button.
3. Try to cut or paste highlighted text.
Options are greyed out (unavaialable)
These actions are only available from the gedit menu.
Options for cut / paste should be available once text is marked.
Hardware: Logitech USB Optical Mouse connected via 4-port USB hub.
I am not parsing what you mean here. You mean on the right-click menu,
the cut/paste options are not enabled?
Here's the behavior I'm seeing - if you highlight a section of text, and
right-click *outside* of the highlighted area or an a highlighted line that has
no text on it (i.e., only a line-break where the highlighting spans the width of
the editing window), it basically de-selects the text, thus disabling the copy
and cut items on the context. Right-clicking *inside* the highlighted area on a
line with text will retain the selection and enable the copy and cut items on
the context menu.
Michael Knepher seems to have put his finger on it. I guess once the pointer
gets _just outside_
the highlighted text, I lose the ability to copy / cut. Since I'm running the
screen at 1024 x 768, it's pretty easy to RMB just after (i.e. *outside of*) the
selected text. Not only that, but once
I highlight my text, doing a right mouse click actually "deselects' the text.
(The text is no longer
I'm reasonably certain that I didn't see this behavoir in Phobe1. e.g. In
Mozilla, or even in
nautilus, I can let my RMB click on white space, and I *still* get the cut /
copy option. Whereas,
with gedit, I have to remember to _keep the mouse pointer within_ the selected text.
The crux of the problem here is the pointer MUST remain _*somewhere* within_ the
OK, thanks. I've reported this as
I'm not sure if this affects the same component, but the same thing occurs in
evolution-1.2.1. I haven't checked any other apps yet.