Thank you for the replies, everyone. I will look into a couple of different options. It seems like the first step is to pick a version control system and then after see what options LyX provides.
Best, Xu On Wed, Nov 9, 2011 at 8:15 AM, Vincent van Ravesteijn <v...@lyx.org> wrote: > Op 9-11-2011 13:51, Stephan Witt schreef: > > Am 09.11.2011 um 11:52 schrieb Vincent van Ravesteijn: >> >> Op 9-11-2011 2:22, Xu Wang schreef: >>> >>>> I'm considering using LyX's built-in version control support. Are there >>>> any drawbacks to using it? Do most people use it? What is the most popular >>>> alternative? >>>> >>> There is no built-in version control in LyX. We just offer easy >>> interaction with the version control that is installed on your system. >>> >>> We also don't want to implement a version control GUI or something like >>> that. There are other applications that are much better for that. You're >>> able to configure the version control support pretty much to use the >>> version control application of your choice. >>> >> Where? I'm not aware of that feature... >> > > You can redefine the menu entries using "vc-command". > > LFUN_VC_COMMAND >> >> * Action Executes external command. This command is intended to support >> additional VCS commands. >> >> * Syntax vc-command <FLAG> <PATH> <COMMAND> >> >> * Params <FLAG>: Flags for the command can be combined together.U - dUmmy >> - no flagsD - Doc - need document loaded to proceedI - dIrty - mark >> document dirtyR - Reload - ensure that the document is saved and reload it >> after command executionM - Message - ask for input string (commit >> message)<PATH>: path where to start. $$p will be replaced by the current >> document path.<COMMAND>: command to execute. $$i/$$p/$$m will be replaced >> by the current document(with absolute path)/path/message. >> >> * Sample vc-command DR $$p "svn up" >> >> * Origin sanda, 13 Jan 2009 >> > > Vincent >
