Apparently, with Obsidian 1.5.0 (Catalyst release), the Files Explorer doesn’t remember what folders were collapse or not …
When closing Obsidian and re-launching it, all the folders in the Files Explorer side pane are now automatically collapsed/folded (which wasn’t the case with Obsidian 1.4.16)
Open a vault and unfold one or more folder(s)/subfolder(s) in the Files Explorer pane
Re-launch Obsidian and open the Files Explorer pane
→ All previously unfolded folder(s)/subfolder(s) are now folded
Did you follow the troubleshooting guide?
Yes : I’ve tested and seen this happen in the Sandbox Vault (Default theme, no css snippet, no plugin) but I’ve never really paid attention to how the Files Explorer was acting there …
So, instead of relying on the Sandbox Vault this time, I’ve relied on an almost empty vault where
Restricted mode is toggled
Default theme +
no css snippet .
I just know for sure that in my vaults, the folded/unfolded state of the folder(s)/subfolder(s) was taken into account by the Files Explorer when (re)launching Obsidian 1.4.16 but it doesn’t seem to be the case anymore with Obsidian 1.5.0.
I would like for Obsidian to remember the folded/unfolded state of my folder(s)/subfolder(s) when (re)launching Obsidian
The folded/unfolded state of my folder(s)/subfolder(s) in Files Explorer is “reset” and all the unfolded folder(s)/subfolder(s) get folded each time I now close and then re-open Obsidian.
Here’s a screenshot of the Files Explorer with some folded and unfolded folders/subfolders before closing Obsidian:
Here’s a screenshot of what the Files Explorer now looks like in the same vault after closing and re-opening Obsidian:
Big Sur 11.7.10 + Obsidian
SYSTEM INFO: Obsidian version: v1.5.0 Installer version: v1.4.13 Operating system: Darwin Kernel Version 20.6.0: Thu Jul 6 22:12:47 PDT 2023; root:xnu-7126.96.36.1992.12~1/RELEASE_X86_64 20.6.0 Login status: logged in Catalyst license: supporter Insider build toggle: on Live preview: on Base theme: adapt to system Community theme: none Snippets enabled: 0 Restricted mode: on RECOMMENDATIONS: none
I must admit that I’ve actually no idea if filing this Bug Report was the thing to do or if I should have created a Feature Request instead …
I mean, I read and re-read the release notes of Obsidian 1.5.0 but couldn’t find anything mentioning the introduction of this new behavior (unless I missed something ) so, I assumed that this change was probably unintentional and possibly a bug …
If it’s not a bug and this change was intentional, I can, of course, open a Feature Request .