Git git git
version control not the epithet
-
-
I prefer more clear turn-based edits to avoid conflict (which is typically what most ppl do regardless, I think?) — but on git with LaTeX it's easy to do concurrent edits if you have separate files for different part of the manuscript (the power LaTeX's input command)!
-
Also to be clear I mean both "conflict" (the interpersonal kind, because I feel concurrent edits are more likely to bring about confusion if not discussed first at least) and "conflicts" when you merge on git.

-
So as with any technology it's a mix of what the user wants and what can be done with the technology. Plain text is undoubtedly the way forward if you want clear and clean git history. A GUI on top of that is what many users want, which is very possible in the case of
@overleaf. -
The reason I don't mention offline GUIs, of which there are a great many and of which some are excellent is because, even though that is how I work, most people (newbies) can't (yet) deal with the overhead of local compilation.
-
Anyway, you are free to DM me (they are open) if anybody wants more coherent and specific advice than can be offered over a bunch of separate tweets.
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.
Still haven’t found a straightforward solution for using Git for papers with lots of co-authors who don’t use Git, however...