More exhaustive Switch File functionality for the C-family
- Total 997
- Win 518
- Mac 202
- Linux 277
|May 28||May 27||May 26||May 25||May 24||May 23||May 22||May 21||May 20||May 19||May 18||May 17||May 16||May 15||May 14||May 13||May 12||May 11||May 10||May 9||May 8||May 7||May 6||May 5||May 4||May 3||May 2||May 1||Apr 30||Apr 29||Apr 28||Apr 27||Apr 26||Apr 25||Apr 24||Apr 23||Apr 22||Apr 21||Apr 20||Apr 19||Apr 18||Apr 17||Apr 16||Apr 15||Apr 14|
A simple plugin that “takes over” the menu item in Goto -> Switch File -> Switch Header/Implementation. Actually, it takes over the command that gets invoked by that menu item.
Just use Switch Header/Implementation like you normally would. That is, either from the menu item in Goto -> Switch File -> Switch Header/Implementation, or by its keybinding, whatever that may be.
For example, if your header file lives in
and your implementation file lives in
then this plugin will actually do the switch.
Two Modes of Operation
When you're in folder mode (you have not opened a
then the plugin will traverse parent directories. A sanity limit of going up
three parent directories is in place. You can change this number in the
settings of the plugin, but do not make this number too high, or Sublime might
If your code base looks like this:
$project_path/include/foo/bar.hpp $project_path/include/foo/baz/bar.hpp $project_path/src/bar.cpp
then switching from
src/bar.cpp, you'll most likely end up in
include/foo/bar.hpp, as that's the first good match. This is the downside of
When you're in project mode (you have opened a
then the plugin will assume that the project file is at the root of the
directory, and the search will start there. All candidate files are collected,
and if there's more than one candidate file, a quick panel will pop up asking
you to select the correct file. From that point on the plugin will always
choose your selection for switching. This mode is much more powerful. Use the
power of the sublime project file.
The plugin might come up with false positives. For example, if your code base looks like this:
$project_path/include/awesome/foo.hpp $project_path/include/awesome/bar/foo.hpp $project_path/src/bar/foo.cpp
then switching from
include/awesome/foo.hpp, it will open
src/bar/foo.cpp is probably paired with