[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows |
Date: |
Tue, 20 Aug 2013 11:38:42 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0 SeaMonkey/2.17.1 |
Follow-up Comment #3, bug #39822 (project octave):
I think my last build is from before that changeset. Maybe tonight I can make
a new build.
It may be wise indeed to set TERM for the Windows GUI.
ESC (forgot that key in previous post): can we invoke the ESC key? In Matlab's
terminal that is used to cancel input at the command prompt (it wipes the
command line clean).
Like you I'd prefer TAB for completion. But maybe it could be made such that
TAB only works for completion if
- focus is in the terminal, and
- there's some text after the command prompt that can be completed at all?
If there's no or too little text at the prompt, TAB could be used instead to
move focus to a next item.
In my original post I briefly referred to the seemingly endless list of items
that TAB moves focus to with a next press. Currently that list is apparently
so long, i.e. all items in the entire GUI?, that for most users the TAB key is
less useful, if not plain useless.
I'd advocate to break up the lists per pane, to use Ctrl-TAB to move to the
next pane/main window (editor, terminal, ...), and to use TAB to switch to the
next item within one pane (button, toolbar, input sub-pane, list, ...), if
applicable. This is the way it works in Matlab as well: Ctrl-TAB for switching
between panes, TAB itself only works in the file browser AFAICS; if focus is
somewhere in a pane, the color of that pane's title bar changes to blue.
In addition, the sequence of where a TAB press would move focus to should be
much more logically structured, transparent for usera, and limited to a
smaller number of items. (I'm afraid that the first could imply re-ordering
some code blocks, right?)
E.g. if TAB moves focus to some toolbar, then it should be possible to
navigate the toolbar buttons with left & right arrow keys.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?39822>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, Philip Nienhuis, 2013/08/19
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, John Donoghue, 2013/08/19
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, John Donoghue, 2013/08/19
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows,
Philip Nienhuis <=
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, Philip Nienhuis, 2013/08/20
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, Mike Miller, 2013/08/20
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, John Donoghue, 2013/08/20
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, John Donoghue, 2013/08/30
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, Philip Nienhuis, 2013/08/31
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, John Donoghue, 2013/08/31
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, Philip Nienhuis, 2013/08/31
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, Philip Nienhuis, 2013/08/31
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, John Donoghue, 2013/08/31
- [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows, Philip Nienhuis, 2013/08/31