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
Improvements to the Ouline Explorer #7971
Comments
#7968 (comment) by @CAM-Gerlach: Of course, the outline explorer is still ordered alphabetically, rather than the order of the tabs in the Editor. Presumably out of scope for now, but if/when you make that change, if would be nice to have the option to either alphabetize it or make it follow the order of the editor, since both could potentially be useful depending on one's workflow. Also, to note, the outline explorer only show Python files, so it isn't a true file switcher for more general cases. Perhaps, as a longer-term idea, we could have an option to show them (just the files without the outlines, of course). |
#7962 (comment) by @ccordoba12 : My recommendation is to highlight the current file and class/method/cell/function by making the selected element to have a different background color, like VSCode does: |
I'd also like to add another suggestion here: Add a fuzzy search widget to filter by file names. |
I found two more that would/could be solved here. And if this is meant to be a "catch all" issue maybe #7976 |
Update: |
@jnsebgosselin Maybe parts of PR #9384 would be useful to adapt for the outline explorer fuzzy search, e.g. the widget itself and the fuzzing code? Perhaps even use unified fuzzing code across our various fuzzy searches (variable explorer, outline, file switcher, completion of possible, etc.)? |
root file item
in the Outline Explorer and to sync the changes with the tabbar of the corresponding EditorStack.Related Issues :
#885, #1986, #2549, #3014, #7053, #7976The text was updated successfully, but these errors were encountered: