Currently, based on observation, not examination of code, it looks like the path from the current file is used. If the current file has no path (untitled), the project path is used. If there is no project path, the home folder is used. So an existing "workaround" to use the last used save-as path is just to not close the last saved file or keep a project file open.

I do think it should be applied before the project path. (@kugel-)

Agree that it needs to be applied before the project path, using the project path is the fallback if this is not set. (@elextr)

When working in a project, I open and save non-project files because it's inconvenient to unload and reload projects. If the save-as path is within the project, it's reasonable to use it instead of the project path. But when going back to editing project files after working on a single out-of-project file, does it really make sense for save as to override the project path with outside project paths?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.