Consider keeping a personal copy under version control. A 'push' script copies to Dropbox, a 'pull' script copies from Dropbox and commits.
-
-
-
If only it were that simple!
-
here is part of that solution (see whole thread though): https://twitter.com/DRMacIver/status/800691765057560576 … Perhaps you have more insight?
-
Looks like you are aiming for perfection... My quick hack didn't solve all issues, but it was way better than pure Dropbox.
-
The background sync is risky. I just did it by hand, like pull and push to GitHub.
-
ah, I see. So you did a diff every time? I guess that might work. Just have to remember to check their dir ever few days, I guess?
-
No need to do a diff, git does it anyway.
-
A pull just copies the files and commits all changes with a default message. You do a pull before editing anything yourself and that's it.
- 6 more replies
New conversation -
-
-
What
@EmilyGorcenski and@DRMacIver said. Keep a local copy with git that you work in, and then sync changes with shared version. -
I'll try, nothing of mine has even been lost though... I'm worried about their contributions... but yes.
-
http://www.phdcomics.com/comics.php?f=1531 … comes to mind.
-
eww phdcomics, but yes, it's what happens & I've used that image in a presentation on (why we need) git.
-
Arguably, git is not a perfect solution for a "rich document editing" workflow. Haven't found one yet.
-
I am talking about code though, but yes, for a document it's tougher if not LaTeX.
-
for code not using any VCS violates good scientific practice, IMHO. But important to pick battles wisely
-
might be better to just work around the problem at this point, and maybe script your sync workflow
- 3 more replies
New conversation -
-
-
..why? privacy? they're not ok with private github repos?
-
they don't want to learn github, I think!? See the threads above for more details.
-
ah.. :/ not even dropbox or something?
-
it's all in the thread haha. Yes, it's on Dropbox that's the problem.
-
see https://twitter.com/DRMacIver/status/800691765057560576 … and rest of the convo.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
INB4: Why? Because collaborators against it.