Someone more geeky than me will confirm or tell me I’ve got it wrong, but:
On the computer that you set up the symlink, you will only see the same icon as an “alias”, not the folder. However, the folder in question will be uploaded to the Dropbox server and copied to any other machine which is sync’ed to it.
While beta testing Scrivener for iOS, I was using symlinks of projects I share with my friend in China—where Dropbox is blocked—in a Dropbox folder while the .scriv projects themselves remained in their shared Cubby. I found that although it apparently worked well, conflicted files were being created whenever I worked on a machine other than my iPad or the MBA with the symlink. The Mac being forgiving about file conflicts, it required looking at the package contents to see this.
Of course, sharing the application support library may introduce other issues in terms of getting the contents of the Dropbox folder sync’d with the application support folder on the second Mac. I’d better have a look at that post by Ioa.
Initially set this up on my MacBook, as detailed above.
On my MacBook Pro, the “ScrivenerLibrary” folder showed up automatically, but had nothing in it. I ran the same code on the MBP and the same shortcuts appeared in the “ScrivenerLibrary” folder. None of the saved compile settings from the MB appeared on the MBP (checking the support folder from the link provided by Scrivener > Reveal Support Folder in Finder).
On my iMac, the “ScrivenerLibrary” folder showed up automatically, but had nothing in it. I have not run the code on the iMac and——as on the MBP——none of the saved compile settings from the MB have appeared on the iMac (checking the support folder from the link provided by Scrivener > Reveal Support Folder in Finder).
When I look at the “ScrivenerLibrary” folder on Dropbox.com, it is empty. I don’t know if it is meant to be empty or not.
The support folder has not appeared on Dropbox.com or in the Dropbox folders on my different Macs.
I move between two or three of the Macs most days and it would make things easier if I could get the support folder to sync automatically.
OK, here’s the thing … I think Ioa must have typed those terminal command details the wrong way round, or you might have mis-read them slightly.
What I did is:
I moved anything from the Scrivener Application support folder that I want to share between Macs into the intended folder in Dropbox—for clarity in what I was doing, I created a /Dropbox/Library/Application Support/Scrivener/ folder so that it mirrors the MacOS library structure, but I don’t suppose that’s important—so for me that was Compile Settings, Layouts, Project Templates and styles.plist
For each of those folders and the styles.plist, in terminal, I typed
then dragged the folder from Dropbox into that command line, followed by dragging the Scrivener folder from the Library/Application Support/ window into the command line, which now read, for instance something like
It works perfectly. Have got the Compile Settings mirroring across the three Macs: change a compile or create a new compile on one Mac and the change / new compile is available in seconds on the other two Macs.
So grateful to you. Will make moving between the machines all the easier, without having to remember to export and import new or updated compiles.
Thank you. I owe you. Hope I can repay you in kind one day.
Thank you, it was a pleasure and no reciprocation is necessary, but if it is needed it will be gratefully received.
I hadn’t tested it in terms of creating a new Compile Setting or modifying an existing one … that was the next step. I found while setting it all up that the iMac here in Exeter didn’t have Adobe Garamond Pro on it—the default font for all my projects except those I share with others, and for my presets—and also that one of my main projects on it was a much earlier version, so I needed to sort those problems out first.
Anyway, I’m really glad it’s working as you expected.
On the question of presets and Scrivener 3, I understand from hints that Keith has dropped, that the new styles system will be project specific—though it seems they won’t apparently be ‘cascading’, i.e. you won’t be able to define one style, say ‘body’ and then define ‘block quote’ and other paragraph styles in terms of that, so that if you change the font of ‘body’, the font of ‘block quote’, etc. will change accordingly. To me, having them cascading is no big deal, but being able to modify a style in a particular project and knowing that that will propagate right through the draft will be really great. I presume also that the implementation of styles will inevitably have a significant effect on the Compile set-up.
Looking forward to Scrivener III. I am confident that Keith will come up with robust and meaningful developments. Imagine it must be close to being released…perhaps in the footsteps of macOS Sierra in a month or so.
Do love tech changes. Something new to learn, absorb, and tweak.
Am also waiting for the new MacBook Pros. Mine dates from 2008. Much loved, but ready for graceful retirement.