…implies there are some sizeable changes. Like many Scrivener Mac users, I use Dropbox to sync my work, as advised by L&L. So before I update, I’m wondering if anyone is using this new Dropbox version successfully with Scriv files.
Thanks everyone for contributing. I did the update and have had no problems. In point of fact, most of my Scriv projects are in Sync (Sync.com) as my Chinese collaborators are blocked from using Dropbox. All the files moved successfully.
As for it now being located in the Library, that just means it appears under “Locations” in Finder sidebars rather than in its former location under “Favourites”. And it is still there in “Favourites” in ForkLift.
Dropbox didn’t roll out this change for my account yet, but if it really shows up under “Locations” now (in the Finder sidebar), it should also be accessible that way: /Volumes/Dropbox (like in “cd /Volumes/Dropbox”). Can anyone confirm this?
Hmmm. Unless Google drive is accessible via “/Volumes” (don’t use it anymore) this means the cloud storage is “not really” mounted like a drive. I don’t understand what Apple tries to achieve here.
But, the Google Gdrive files are accessed just like explained above for Dropbox. I have Hazel rules which pointed to to the old locations and by repointing to the new locations everything works. A special “mount” available on terminal commands is not essential since they provide and document the location in the file system.
I know nothing about how or why Apple changed their spec or rules. Surely documented somewhere as Dropbox, Google, and Microsoft changed to conform.
Frankly, it really all just works and by reading the documentation there are no mysteries.
It’s a case of “why should I?” Having had to contant Dropbox support in the past I am neither comfortable nor hopeful that Dropbox has considered those of us who use Terminal to do stuff.
Their earlier change in which they sneaked out online-only as default does not fill me with any confidence.
As you are a command line user in a terminal (as am I), perhaps you can experiment with symbolic links (or similar) pointing to the new Dropbox folder locations. This could simplify the change you distrust. I’ve not tried this as I don’t have great interest, so over to you.