Actually I am new to Subversion. Shortly speaking, Subversion is a tool to manage versioning of documents, especially for software developers. You can find the details here.

I have a team to write a book using LaTeX, each member can create, update and delete the supporting files. To avoid any loss of data, I want to manage the synchronization using Subversion.

Is there a LaTeX editor supporting Subversion out of the box?

EDIT 1: Thanks all for your response. I just wait for a couple of days to get more options from others. Then I will mark as the answer, of course not so objective :D


12 Answers 12


Use the same editor you are using today, and use subversion with tortoise svn. Tortoise is a simple and good windows explorer extension.

  • I agree wit Johan. I use subversion for software development and I think this is the best solution, you can keep using the editor that best suites your needs and have the benefits of svn at the same time. You may be losing some good features of an editor that doesn't have built-in svn, it's not worthy.
    – Nico
    Apr 4, 2013 at 12:25

I wish I could say TeXShop, my editor of choice, but I can't. There's always emacs and Eclipse.

  • 6
    Eclipse is available on Windows, is it not? Nov 29, 2010 at 3:42
  • 7
    Emacs is also available on Windows. Nov 29, 2010 at 5:19
  • 1
    Thank you @Matthew Leingang and @Mikael Vejdemo-Johansson for the response. I will figure out those to find one suits my need. Nov 29, 2010 at 5:34

Auctex on Emacs:

  1. SubVersion, Emacs Wiki page;
  2. Auctex, same place.

The other editor, Vim, has a Subversion plugin. Vim does have special support for editing Latex &c, but it's not such a polished offering.

Both Emacs and Vim work well on Windows. Take a look at the GNU FAQ for Emacs on Windows.


TeXstudio is a LaTeX IDE that has built in support for Subversion. I've not used it with Subversion myself, preferring Mercurial, so cannot vouch for how good its support is.

SVN Options

File - SVN


In addition to the usual suspects (vim, emacs, etc.), for editors actually designed for LaTeX in particular, I believe jLaTeXEditor does. I don't use it personally, however.


I use WinEdt on my Windows XP. There's a component for SVN which you can easily add:


It works fine with Tortoise SVN (for Windows).


Eclipse + Texlipse + Subversive is the best option in my opinion. You need to download and unpack eclipse first. Then you can simply install the texlipse and subversive plugins. If you are familiar with eclipse, texlipse is surely the best tex editor for you. If not, it will surely be useful since eclipse does have a plugin for every file format under the sun. Furthermore, it is multiplatform and it has a built-in compare capability. By the way, eclipse keeps a local history for every file being edited automatically. So, if you are the only person who is working on the tex project, you may not need to install subversion at all. See here.


BBEdit of course! Sometimes I need to edit TeX files in BBEdit rather TeXShop. Then I use a script that calls TeXShop for typesetting and previewing PDF files. There is a Subversion Menu in BBEdit.


The two plugins available for Eclipse's SVN support are sub-par at best, and dangerous at worst. I personally prefer using TortoiseSVN and my favourite LaTeX editor.


You could use Geany. It's not really a LaTeX editor but rather a simple yet powerfull text editor / IDE that is not as overwhelming and huge as Eclipse might be. It has plugins for LaTeX and version control that includes SVN.


I wrote myself a small bash script using the inotify-tools (see this unix.SE question), which does the following things every time I save a file (you can also have it watch an entire directory/tree):

  • git commit -am"autocommit" (you'd replace this by svn, though you should really consider git instead...)
  • latex (or pdflatex)
  • view the compiled document, or trigger the opened viewer to reload the file if needed
  • if compilation failed, git commit --amend -m"autocommit, not compiling" (alternatively, you could only commit on successful compilation)

Now I can track down to the minute when I did change what in my Diplom thesis... (And the repository is still very small despite my including all used images)

  • 1
    Here's a nice post about git+latex Mar 14, 2013 at 10:19
  • This is wrong, IMO. You do not want to create a commit every time singleyou save.
    – jub0bs
    Jul 1, 2014 at 21:54
  • @Jubobs it's better than no commits at all though. I currently have TeXnicCenter set up to commit on each compile, but amend if the last commit failed, which is slightly better than my original suggestion. of course you can still use git rebase later on to merge commits into more significant hunks. But honestly, with very few exceptions I never used my repo for anything but a simple rewind, for which the auto-commit works just fine Jul 2, 2014 at 5:16

You could consider an ownCloud installation - it supports file versioning and can be mounted through WebDAV as a drive. If you have some cheap hosting, it is quite easy to work with, and a lot of people do. I have used it for this kind of thing.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .