Alt+Up and Alt+Down do not control history when interactive window launches pinned.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Reproduce the pinned C# interactive window workflow described in the issue, then inspect the CommandFilter handling for VsStd12 and MoveSelLinesUp. Compare command routing before and after relaunch; done means Alt+Up and Alt+Down navigate interactive history when the window is restored from a pinned tab.
Written by the indexing model from the issue text.
Description
Reported at developer community as https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1178927.
Workflow:
- Open VS and dock the C# interactive window to one of the edges.
- Pin the window so that it collapses to a tab on the edge.
- Close VS
- Open VS
- Show the C# interactive window by clicking the tab
- Execute
var a = 5; - Press Alt + Up
Expected Outcome:
The current line should match the previous entry and read var a = 5;
Actual Outcome:
No change to the current line. From debugging the CommandFilter, pguidCmdGroup is VsStd12 and the nCmdID is MoveSelLinesUp.
- Dominant language
- C#
- Stars
- 78
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 dotnet/interactive-window
-
dotnet/interactive-window#255 · 2 comments · 6 reactions · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dotnet/interactive-window#241 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
dotnet/interactive-window#230 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dotnet/interactive-window#185 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dotnet/interactive-window#184 ·
All issues in dotnet/interactive-window
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·