Summary:
I’m suggesting a Unified Context Search feature that builds on the existing “@” context search. This would consolidate file, code, symbol, and directory navigation into a single, context-aware search tool, simplifying navigation and improving productivity for developers.
Details:
Currently, developers rely on different shortcuts for various searches:
- File Navigation:
Ctrl + P
to open files. - Code Search:
Ctrl + Shift + F
to search for code snippets across the workspace. - Symbol Lookup:
Ctrl + T
to find functions, classes, or variables.
With the Unified Context Search, these features would be merged into a single interface:
- File Navigation: Searching for a file would open it directly.
- Code Search: Searching for code snippets would navigate to the specific line containing the keyword or snippet.
- Symbol Lookup: Searching for functions, classes, or variables would jump to their definitions.
- Directory Search: Searching for a directory would focus that directory inside the file explorer, rather than opening it as a file.
This unified search would be accessible using a single shortcut (e.g., Ctrl + K
), allowing for seamless navigation across the entire project.
This would provide a unified interface for searching, similar to the existing “@” context search, but expanded to cover files, code, symbols, and directories.
Why It Matters:
Switching between different shortcuts and search tools interrupts the workflow. A Unified Context Search would make navigating through files, directories, functions, and code faster and more efficient. This improvement would save time, reduce friction, and enhance productivity for developers working on large projects.