#3015 commandline to don't create backup (suggestion #3400305)

2.16.0
open
nobody
5
2013-03-02
2012-11-05
Rodrigo Cesar
No

Implemented commandline switch "-nobakup". When the application get this commandline option the backup file is not created. Even if the user options is marked to generate backup files.
This will be useful when we don't want to generate backup file on resolving conflict files into versioned folders. The backup file into a versioned folder is not necessary.
So, we can use the below command line to resolve conflict files without the needing to uncheck the general option to generate backup file.
---------------------------------------------------------
WinMerge[U] conflictfile [/nobackup]
---------------------------------------------------------
The param name (nobackup) and the internal variable names could be changed.
I was not able to test! I'm getting a compilation error (LNK1181: cannot open input file 'libexpat.lib') over Visual Studio 2010. But it is a minor change that possibly will work.

Made over WinMerge Version = "2.15.1"

Discussion

  • Rodrigo Cesar
    Rodrigo Cesar
    2012-11-05

    TortoiseSVN patchfile

     
    Attachments
  • Rodrigo Cesar
    Rodrigo Cesar
    2012-11-08

    • summary: commandline option to don't create backup --> commandline to don't create backup (suggestion #3400305)
     
  • Christian List
    Christian List
    2013-03-02

    • milestone: Trunk --> 2.16.0
     
  • Christian List
    Christian List
    2013-03-02

    Not a bad idea. I've marked it for the 2.16.0 release for now.

    I wonder if we could come up with something shorter than -nobackup to match the other command line parameters we have.