gedit search function is not practical anymore
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gedit |
New
|
Unknown
|
|||
gedit (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
i use gedit a lot, and i find it comfortable in general.
the new small search window is extremely impractical. FOCUS PROBLEM:
CTRL+F > type a search (search of longer strings FAR TOO SLOW) > find
and now, typing ESC brings one back to the former place!
when trying to use CTRL-F again, the search string is replaced by new text.
if one wants to stay in the found passage, one must use the mouse/touchpad to click into the text.
this is an extremely annoying feature/behavior.
i simply would like to have the old search window + its behavior back.
i am working very quickly and mostly using shortcuts.
gedit now completely interrupts my way of working.
additionally, where are the other search functions such as case-sensitive search?
additionally, i do not want the search function to slow down so much. for me it is ok to start the search after i have finished typing my search string :-) this new energy-consuming ZEITGEIST-
best wishes, vollmanr
Changed in gedit: | |
status: | Unknown → New |
related to this https:/ /live.gnome. org/Gedit/ FAQ ?
gedit is very slow and/or crashes when opening files with very long lines. Can you fix it?
When designing GtkTextView (the text display widget of gtk+ which gedit uses) the developers had to make a design decision: trading off bad performance and memory use on corner cases like very long lines in exchange for better performance in search operations and full support for UTF-8 text. This is a known limitation of GtkTextView and cannot be fixed. On top of that Pango seems to use a lot of CPU drawing such long lines. This may be fixable, but it isn't easy... Feel free to give it a try. Crashes with long lines are usually due to out-of-memory conditions, but if that's not the case then we would like to know about it.
------------
I think I've suffered from the long-line issue a lot, and have used leafpad (and am about to try geany) as a more reliable alternative; don't get me wrong: if gedit were reliably stable and would not become UNUSABLE for certain documents, I'd have zero complaints about it...