[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53657] Ambiguous 'Ctrl+F' shortcut

From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #53657] Ambiguous 'Ctrl+F' shortcut
Date: Sun, 15 Apr 2018 12:13:43 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Follow-up Comment #3, bug #53657 (project octave):

4.3.90 candidate.  OK, looking at tags in thg interface, that is prior to the
bug fix that I linked to.

However, in my testing here with the latest stable version I'm seeing some
annoying bugs concerning the Editor's Ctrl+F find behavior.  Ctrl+F, Ctrl+G,
Ctrl+Shift+G and Escape all work, but the context in which they are active is
dependent on which window has focus.  The way I currently see this is
practically an unusable search.

When Editor is docked and focused, Ctrl+F opens a dialog search window. 
Ctrl+G, Ctrl+Shift+G and Escape all work when the dialog window has focus. 
But if clicking in the Editor to focus, these three no long work.  It would be
nice if they did because then those shortcuts would still work even though the
dialog box is closed.  (See the Documentation window behavior, and note that
FireFox browser does the same thing...Ctrl+G still works after closing its
"find footer".)

When Editor is floating, Ctrl+F also opens a dialog search window, but the
situation is worse in the sense that the floated Editor window moves behind
the main Octave GUI window.  Trying to get the Editor window and search dialog
box visible at the same time doesn't work.

It appears to me that the Editor's Ctrl+F search dialog box has the wrong
parent (the main GUI window) when it should be the Editor window as parent.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]