Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy
by wiz21c on Monday August 09, 2021 @05:28AM
(#28114373)
my workflow is different : we use voice chat to share and we edit collaboratively. Both these allow to actually work together and, more importantly, think together.
Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy
by ranaexmachina on Friday August 13, 2021 @03:48AM
(#28166526)
That's very interesting. I honestly didn't think of that, since we often worked asynchronously or at the same machine (which doesn't work at the moment, of course). I can see how Overleaf can be nice for that purpose.
This kind of workflow is not really usable with Overleaf. Overleaf uses Git in the background, but every commit is named "changes on Overleaf" and the individual commits do not really make much sense. In addition, everything is immediately put into the master branch and there's no way to summarize or group changes (like with commits and/or pull requests).
My next problem is, that Overleaf just uses latexmk so if you have some code to generate graphics or tables, you have to compile and add them manually all the time.