3 ms·

> Maybe other tools do some of these things, but having all of them in place is nice. Emacs. I have almost everything you mentioned out of the box with doom Em

> Maybe other tools do some of these things, but having all of them in place is nice. Emacs. I have almost everything you mentioned out of the box with doom Emacs, and the other stuff should be trivial if it doesn't already exist.

abhgh 2y ago
The big hurdle now becomes that all collaborators now need to know emacs;-) But good to know! Although I am curious as to how clicking on TeX leading to scrolling the PDF to the corresponding location in the PDF would work (and vice-versa). Also for collaboration (some of my collaborators are not in the same continent) I'm assuming you need to host an emacs server; where might one typically do this? Any cloud compute provider, e.g., Linode?
- ramenbytes 2y ago
  > The big hurdle now becomes that all collaborators now need to know emacs;-) As God intended. ;) They actually don't though, if they prefer to remain heathens see bottom of this reply. > Although I am curious as to how clicking on TeX leading to scrolling the PDF to the corresponding location in the PDF would work (and vice-versa). Could be wrong, but I think the synchtex files produced by builds are for that. I usually have the PDF open in one Emacs buffer (you can view pdfs in Emacs), and the TeX file open in another. Ctrl-left click in the PDF jumps to the spot in the text buffer for that spot in the PDF, and in the TeX buffer there is a keybinding to do the reverse. Probably a way to click and get there too, but I use the keybinding. > I'm assuming you need to host an emacs server No, Emacs runs locally and interfaces with the cloned git repo on your machine. Your collaborators could use Notepad for all Emacs cares, as long as they work in the same repo and push to the shared remote.
  - abhgh 2y ago
    Wasn't aware of synchtex - read up on it a bit based on your comment, yes it looks like that might work, thanks! For collaboration, I meant real-time collaboration, where you see your collaborator's cursor or changes while you are on the document yourself. Git push/pull probably won't suffice for that, but yes, while convenient, the larger question is if all projects even need that kind of collaboration.

abhgh 2y ago

The big hurdle now becomes that all collaborators now need to know emacs;-) But good to know! Although I am curious as to how clicking on TeX leading to scrolling the PDF to the corresponding location in the PDF would work (and vice-versa). Also for collaboration (some of my collaborators are not in the same continent) I'm assuming you need to host an emacs server; where might one typically do this? Any cloud compute provider, e.g., Linode?

ramenbytes 2y ago
> The big hurdle now becomes that all collaborators now need to know emacs;-) As God intended. ;) They actually don't though, if they prefer to remain heathens see bottom of this reply. > Although I am curious as to how clicking on TeX leading to scrolling the PDF to the corresponding location in the PDF would work (and vice-versa). Could be wrong, but I think the synchtex files produced by builds are for that. I usually have the PDF open in one Emacs buffer (you can view pdfs in Emacs), and the TeX file open in another. Ctrl-left click in the PDF jumps to the spot in the text buffer for that spot in the PDF, and in the TeX buffer there is a keybinding to do the reverse. Probably a way to click and get there too, but I use the keybinding. > I'm assuming you need to host an emacs server No, Emacs runs locally and interfaces with the cloned git repo on your machine. Your collaborators could use Notepad for all Emacs cares, as long as they work in the same repo and push to the shared remote.
- abhgh 2y ago
  Wasn't aware of synchtex - read up on it a bit based on your comment, yes it looks like that might work, thanks! For collaboration, I meant real-time collaboration, where you see your collaborator's cursor or changes while you are on the document yourself. Git push/pull probably won't suffice for that, but yes, while convenient, the larger question is if all projects even need that kind of collaboration.