Some news... Very pleased to announce that today was just a normal day. I spent 20 minutes figuring out whether “latest_version.doc” or “latest_MS.doc” was the latest version, reset my online manuscript submission password, and googled “R stats chi test” for the umpteenth time
-
-
I’m a big fan of overleaf!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This being said, I am working ATM on a manuscript with more authors that is on
@overleaf and where all of us are using the GUI because we don't do turn-based edits as I am used to, so I use the GUI (it's still versioned on git ofc). -
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 -
-
-
I would much prefer this option indeed but I would end up most of time teaching latex.

-
I don't know I am so lucky that they all just accept using LaTeX. Maybe I'm a very convincing person.

-
"so how SURE exactly are you want to use Word to write this article with me?"pic.twitter.com/8WlwNE9e5X
-
I have had very short "classes" with some fellow lab members and coauthors. But they all seem to want to use LaTeX. I offer to do all the formatting which I'm sure helps. I think maybe it's "cool" (which I find hilarious as it's def not when I have to write a for loop in LaTeX)?
-
Ha OK. I guess that if you take the formatting off in charge that makes the whole thing more appealing.
-
You can't realistically ask people to change their workflow without doing something in return! Basic psychology LMAO!

-
Yes it make sense but your workload must go through the roof, no? Though this is definitely a good way to become a latex wizard / enchantress.




-
I think it depends. I mean if they can start off just writing plain text in .tex files and then compiling them (say on
@overleaf) it's not a small step (esp. for scientists) to actually start learning on their own. - 3 more replies
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.
version control not the epithet
Still haven’t found a straightforward solution for using Git for papers with lots of co-authors who don’t use Git, however...