You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
I'm not sure we would always want to have this behavior. There are times when I want to open a file that is outside my current project, just so I can look at it for reference. In that case, I don't want my current project to change.
Also, it may be odd to have this behavior at startup time, but not if Brackets is already running.
Removing the "starter bug" label and adding "move to backlog" since this should have more design work before it is implemented.
Added a generalized version of this idea as https://trello.com/c/f6G3NiwS. I agree with Glenn that this might not be what we want for default behavior, but the general workflow of starting by opening with some random file, and then quickly wanting to open one of its parent folders (either an existing project or as a new project), seems valuable.
This was introduced with these pull requests: #2653, adobe/brackets-shell#190
If Brackets is not open,
and you drop a file on it which causes Brackets to startup,
and the file exists in a project in recent project list...
...it would be nice if Brackets switched to that project.
The text was updated successfully, but these errors were encountered: