Currently, when you try to quickly open a repository (exploiting fuzzy search), the actual Git folder name is the reference for the repository.
It would be nice if we could have a field to assign a custom name to each repository, because often different repositories have same folder names.
Example, I manually clone a ST package for AsciiDoc in Packages\AsciiDoc (although the repository might be called Sublime-Asciidoc I want to use a custom folder naming and avoid the redudnant “Sublime-” part).
But then, asciidoc is likely to show up in many Git repository folders, which makes it difficoult to pin-point which one to open via fuzzy search in SM open functionality.
Being able to associate each folder to a meaningful name would be better, especially if there’s a ST associated project with the same name.
In ST projects we can easily control the project name shown in “Quick Switch” by giving a custom name to the .sublime-project file.
It should be possible to achieve something similar in SM somwhow.
What about having a SM setting file in the repository root? Eg: .sublime-merge which could be used to store some settings.
Or maybe, having a JSON settings file to control which repositories are shown in the “Switch repository” dialog.
I also think that both ST and SM should offer a native dialog to control which projects/repository are shown in the “Quick switch” dialogue, and most of all to allow editing the entries (change paths, delete old projects, rename them, ecc.).
It’s common that project folders get moved around when they shift from draft to production, and currently there’s no easy way to udpate them in the “Quick switch” dialogs except by editing the .sublime_session files in %AppData% — which is not practical at all because:
- It’s easy to corrupt the file and loose all the records of projects/repos.
- It requires closing ST and SM.