We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to "New". Thanks again!
** Changed in: gedit (Ubuntu)
Status: Incomplete => Invalid
** Changed in: gedit (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/670341
Title:
"Find" keyboard shortcut does not deliver subsequent keypresses into
Find dialogue box
Status in “gedit” package in Ubuntu:
Fix Released
Bug description:
Binary package hint: gedit
When using the keyboard shortcut to "Find" text, it is usual to deploy
it on the fly. That is, seemlessly. There is unfortunately a seem in
Gedit's Find shortcut.
The process, while in the midst of working in the text editor, takes a
split second, and it usually goes like this:
- Establish a need to find text
- Press the keyboard shortcut to "Find"
- Enter the text to be found
- Press return
- Find the text
- Continue working
Gedit, however, does not capture keypresses made immediately following
the invocation of the Find function with the keyboard shortcut. It
begins capturing keypresses and putting them in the "Search" field of
the "Find" dialogue only after the dialogue has opened.
Since the dialogue can take a while to open there is an unnatural
pause between the Find invocation and the dialogue's appearance. Any
keypresses that are made in this space are channelled into whatever
document is open in Gedit.
But it is normal to start typing the text to be found immediately
after the Find function has been invoked with the keyboard shortcut.
It is not only frustrating to have to wait for the dialogue to open,
it is unintuitive.
The result is that text intended for the Search field is forever being
entered the document because the Find function is taking too long to
catch up.
The resulting processes looks like this:
- Establish a need to find text
- Press the keyboard shortcut to "Find"
- Enter the text to be found
- See that the Find dialogue has opened slowly and the find text has not
appeared in the Search field
- Press Esc to close the Find dialogue again
- Delete the text that has been put in the document instead of the Find
dialogue
- Press the keyboard shortcut to "Find" again
- What patiently for the Find dialogue to open
- Enter the text to be found
- Press return
- Find the text
- Continue working
You might think that I should learn to wait. But I do find this is
happening time and again because I have an unshakable expectation that
keypresses made after the invocation of a function will go to that
function.
Or this may be because my machine is slow. This should not, however,
prevent my keypresses being captured at the right time and put in the
right place so that my use of the keyboard operates as it ought, which
is seemlessly.
Excellent text editor all the same.
Markling.
ProblemType: Bug
Architecture: i386
Date: Wed Nov 3 11:49:56 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: gedit 2.28.0-0ubuntu2
ProcEnviron:
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-22.67-generic
SourcePackage: gedit
Uname: Linux 2.6.31-22-generic i686
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/670341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
