[quote=“jps”]Thanks again for the above bug reports.
[quote=“jbjornson”]- As mentioned by others, I agree that the project specification and the project state should be stored separately (maybe sublime-project and sublime-workspace?). As it is now, it will be difficult to edit the project files (because there is so much state information stored there) and sharing projects doesn’t make much sense. The simplicity of the old project files was great but I really like the features of the new projects. Can’t we have the best of both worlds?
- sublime-project: build_system, folders, save_all_on_build, plus any include/exclude instructions[/quote]
It may be worth doing this, but I’m concerned about confusing people: people may not know what a ‘workspace’ is, so they use the project functionality when they’d be better served by using workspaces.[/quote]
I think ‘project’ files and ‘session’ files are the correct distinctions here. Session info was stored in 1.x as well, but was a global thing. I like the new project/session stuff, but it has its downfalls as well.
One of the things that annoys me about this new implementation is when I wanna reference a file from another project (B). In the past, I would switch to the other project (B), open the file with the fuzzy finder, and then switch back to (A). The new behavior closes the file of interest when I switch back to (A).