Pane focus movement doesn't remember where it came from
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the vertical-then-horizontal pane layout from the issue and follow the moveFocus right, down, left, right sequence. Trace the pane-focus movement entry point and verify that the final right move returns to pane 3 rather than pane 2; done means the described focus sequence behaves as expected.
Written by the indexing model from the issue text.
Description
Steps to reproduce
create a vertical split, then on the right pane, create a horizontal split
somewhat like this :
|-----------|
| | 2 |
| 1 |______|
| | 3 |
|____|______|
if you move focus from 1 to 2 by moveFocus right
then move focus from 2 to 3 by moveFocus down
then move focus from 3 to 1 by moveFocus left
then moveFocus right
Expected behavior
The focus should go back to 3. Otherwise toggling between 1 and 3 becomes a painful, especially if 2 is ends up more complicated with more panes.
Actual behavior
focus goes to 2
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/terminal
-
Area-Settings Issue-Bug Priority-3 Product-Terminal
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Area-Schema Help Wanted In-PR Issue-Task Product-Terminal
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Issue-Feature Needs-Tag-Fix Needs-Triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Issue-Feature Needs-Tag-Fix Needs-Triage
Difficulty 3/5 1-2 days Newbie friendliness 66/100
-
Issue-Bug Needs-Triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in microsoft/terminal
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·