If you have an accent, and doesn’t want to check all file, you can use (on windows) the cool app named PowerRename ( from powertoys). So, if Working Copy doesn’t work with synced vault, and your language use accent, it’s probably that (fact : I literally don’t see accent because of habit). Okay, thanks to ( see this post), I finally understand why my vault and folder doesn’t want to sync with Working Copy : Accented name. These are all Working Copy side problems though, so perhaps things will improve in the future. But it’s certainly not a process I’d recommend for someone who doesn’t have a lot of patience or isn’t already comfortable with the basics of Git. I don’t move files like images, PDFs, and videos much, and day-to-day things work fine for me. That said, I ran into this during migration. So syncing lots of changes with files stored in LFS can mean multiple tries to get a good pull, and sometimes reverts to clean up after folder sync tries to be a little too smart. The LFS download process seems to keep running even when Working Copy takes an error, but sometimes the folder sync will kick off before this is finished and there will re-add files you’ve moved to their old location. Large numbers of new files, or even moves of existing files, seem to cause timeouts. The biggest thing I’ve noticed for anyone interesting in using Obsidian + Working Copy + Git LFS to store and sync large vaults is that the Working Copy LFS support seems really touchy. But as a manual flow using the Git command-line app, it works. I’m not using the Obsidian-git plugin, as I generally prefer to keep things a bit more manual, so I can’t speak to the LFS issue there. I just wanted to report back here with my LFS experiments.
0 Comments
Leave a Reply. |