“Excluded files” option doesn’t quite work for me as the most annoying features of having an unwillingly indexed folder for me are not excluded from parsers
Use case or problem
Im currently hosting my obsidian vault in Mega, Mega currently uses a folder called “Rubbish” for local cache, hosted, in this case, inside the vault.
The rubbish folder i cannot deactivate in any way nor rename it to “.rubbish” (for obsidian to ignore it) as the service just creates a “rubbish” folder again
Problem is, that while the native “Excluded files” option takes care of search, graph view and unlinked mentions, the more apparent problems of this peculiar inconvenience stay, as:
When opening ‘backlinks’ pane on a certain file (ie. a daily note) under linked mentions appears 10, or 20 notes with the same name as, besides the correct linked note, they are 10+ backups on the unwillingly indexed folder
When linking to a note that has a duplicate in the unwillingly indexed folder (almost every note), the link shows the long path (as it needs to differentiate from the multiple backups) thus links appear excessively long instead of just the name of the file
The backups, although less noticeable, are still visible in link suggestions, making them more prone to human error linking them instead of the current version
And of course, it appears on the files pane, i’ve tried the hide files plugin, but weirldy enough it doesnt work after restarting obsidian
an option to fully ignore a path from all obsidian parsing/indexing
an option to designate a backup folder (as the .trash folder natively does for obsidian) to ignore it from all parsing/indexing
flags/options for the user to decide which indexers will ignore/ still work/ still work but in a lesser extent, under the excluded files section, instead of a fully curated option
I have a similar problem. I have very large folders than need to fall within the scope of my vault (for other unrelated reasons), but which are never needed in obsidian and just drastically slow down opening and indexing time. Having a proper way of excluding folders or paths from being index would massively improve performances for someone like me (and that’s not helped by the fact that I also already have quite a large note vault with a couple thousand files and figures referenced)
I have a similar problem with a mono repository. Yarn adds a big node_modules folder with 250k files and 6000 markdown files. I can neither delete it, nor rename it, because it’s maintained by yarn. Obsidian chokes under the huge amount of files.
So I’m aware of the Files & Links > Excluded files feature, and have seen several other threads here discussing specific needs like excluding a path from quick view results, but not addressing a general need to make certain paths invisible to Obsidian entirely.
Use case or problem
I want to use Obsidian to manage / author documentation in my git repos for various development projects. The git repos would exist as subdirectories (submodules) underneath my Obsidian vault. I plan to use the Obsidian Git plugin to sync.
The problem is that in the git repositories, my other working files also exist and Obsidian looks at all of them, everywhere. I really only want Obsidian to deal with markdown files and selected other files. Attachments would specifically be stored under attachments dirs.
The result of this is that Obsidian indexes thousands of files that I don’t care about… like READMEs in node_modules etc… and it ends up unusably slow. To the point where file operations take upwards of 10s to complete.
I imagine that this is a fairly huge blocker for any developer who wants to seriously use Obsidian to support documentation in their working repositories, which is where Obsidian would really shine - documentation is often hard to make sense of in dev repos.
I’m happy to tell Obsidian where to look or not look. I’ve already configured the Excluded files feature with Regex accordingly, but it seems to make no difference to what Obsidian indexes.
The .obsidianignore file that was recommended in another thread is a great idea.
Another option is to enable a ‘Whitelist’ mode, where Obsidian starts off indexing nothing, and you specifically give it paths in glob syntax to include.
Also, configuring Obsidian to respect .gitignore would be incredibly useful.
Current workaround (optional)
I haven’t found a way around this. I’ve tried the existing features (that I know about) to no avail.
Off the top of my head, symlinks can’t filter the contents they are symlinking to, or be overlayed, so it would require the duplication of the repo’s directory structure in the Obsidian vault, and the symlinking of each individual file that’s to be included.
Also look at overlayfs which is mentioned in your link, but that also seems to lack the ability to filter paths that are overlayed.
It’s an interesting direction to go…
Still would be far simpler having a .obsidianignore file and respecting .gitignore.
+1 from my side. In my case I’d like to have some 3rd party tools in the vault which require symlinks to system files which require special previleges. This is even worse than long waiting times for commands, since Obsidian simply fails indexing all the files at startup, reports an error and dies. Having the option to truely ignore files and folders would thus be very helpful.
I think both a toggle in the Excluded files list and .obsidianignore files would be good solutions. As a git person, I favor the latter but have to admit that the former better fits the feel of obsidian.
That is only a workaround, which works differently on each platform, think mobile or windows (where SymLinks have to be enabled by an Admin).
We need something built-in that works the same across all platforms.
+1 here; I’d love to use obsidian to connect all of the projects and notes in my PhD work - many of which are repositories themselves with i.e. node_modules/ … I’ve used regex to ignore most of these but obsidian still sucks down 5gb of RAM and has to re-index 14k files each time I open it, then has boggy performance afterwards.
I would second a kind of .obsidianignore file type, that seems like a smart and well-understood solution, though perhaps just by the git-folks community.
Maybe I misunderstood something from that post and this feature but after facing the same issue with docusaurus and hugo projects I took the problem from a different perspective.
With docusaurus where I simply bind my mardown directory (in that case) ./blog ./docs and ./src in my Obsidian Vault which give something like this
Obisidian Vault = $HOME/Vaults/*
Static Website = $HOME/Public/*
sudo mount -B $HOME/Vaults/website.tld/blog $HOME/Public/website.tld/blog
sudo mount -B $HOME/Vaults/website.tld/docs $HOME/Public/website.tld/docs
sudo mount -B $HOME/Vaults/website.tld/src $HOME/Public/website.tld/src
and so; obviously it is tight to the user (via a script) or the machine (via /etc/fstab) but it works well
Out of my head, it is also possible to relay on git and is submodule power
like in both project
Obsidian and Hugo you have a git repo for them and the content of your post are managed as a submodule of them