Closed dm0 closed 5 years ago
Projects in the global config - it's just a filter. Not required to list all projects there.
I'll think about the usability of projects without real files (just tabs) :)
P.S. And we'll lose the possibility to open some issues from several projects inside one window, right?
Yes, I understand that it's just a filter, but for me it takes too long to open project selection dialog. For example to the moment it is running already for about to 5 minutes and still hasn't displayed the dialog (I chose Gitlab project: Issues). I don't know why -- maybe I have too many projects available. So for me setting a filter is something very important.
Actually I didn't mean projects without files. My typical use case is when I have ST project for each Gitlab project.
So I see it this way: In ST project I set filter corresponding to Gitlab project (or several related projects).
If I don't set per-project filter then global settings are in effect, and I can work with all available Gitlab projects (if they start to work for me).
Also I find setup with single project quite useful -- this way I don't have to select project in popup dialog and it saves some time.
Thanks a lot!
It would be nice if the package could read settings (in particular
project_filter
) from ST project file (.sublime-project
).It will make it possible to work with different projects in sublime without listing all of them in global package config and to easily switch between gitlab projects.
Thanks.