Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Debug Console command history suggestions in chronolological order instead of alphabetical order #148072

Closed
ssavary opened this issue Apr 25, 2022 · 1 comment · Fixed by #165549
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues insiders-released Patch has been released in VS Code Insiders polish Cleanup and polish issue
Milestone

Comments

@ssavary
Copy link

ssavary commented Apr 25, 2022

When I start to type a command in the Debug Console, it suggests matching entries from my command history, which is great. However, the suggestions are presented in alphabetical order, instead of chronological order, which would be more intuitive. Most of the time, the debug console history is full of mistyped commands or iterations over the same function calls, and alphabetical order does not make sense here. Moreover, since the display of the preview of the command is shortened in the suggestion list, it is difficult (or impossible) to distinguish between many similar-looking commands. Having them listed from the newest to the oldest would clearly improve usability.

@ssavary ssavary changed the title Debug Console command history suggestions in chronolological order Debug Console command history suggestions in chronolological order instead of alphabetical order Apr 25, 2022
@ssavary ssavary changed the title Debug Console command history suggestions in chronolological order instead of alphabetical order Feature request: Debug Console command history suggestions in chronolological order instead of alphabetical order Jun 16, 2022
@weinand weinand added the debug Debug viewlet, configurations, breakpoints, adapter issues label Oct 19, 2022
@weinand weinand assigned roblourens and unassigned weinand Oct 19, 2022
@roblourens
Copy link
Member

I don't have total control over the order of the filtered contents of the suggest widget currently, so we can't put history in a separate section and set the order. Because of this I find console history to be not that useful and I generally disable it: "debug.console.historySuggestions": false.

However, it seems when commands are otherwise a tie in fuzzy filtering, I can change the order of the tie-breaking. For example, I evaluated in this order

  1. evaluated1
  2. evaluated2
  3. evaluated3
  4. zEvaluated3

the first 3 that tie are sorted in recency order but the last is forced to the bottom due to being a worse match. Does this help at all?

image

If not what you had in mind, maybe give an example

@roblourens roblourens added info-needed Issue requires more information from poster polish Cleanup and polish issue and removed info-needed Issue requires more information from poster labels Nov 4, 2022
@roblourens roblourens added this to the November 2022 milestone Nov 4, 2022
@VSCodeTriageBot VSCodeTriageBot added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Nov 4, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Dec 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues insiders-released Patch has been released in VS Code Insiders polish Cleanup and polish issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants