Author Topic: vsdiff sometimes can't find second file on command line  (Read 1565 times)

twaithrb

  • Community Member
  • Posts: 28
  • Hero Points: 0
vsdiff sometimes can't find second file on command line
« on: June 05, 2013, 05:48:38 pm »
When attempting to compare two files using vsdiff from a command line, if the second file specification is exactly 16 characters long, the 16th character is being dropped and vsdiff displays a popup reporting the file (minus the 16th character) can't be found.  I recently noticed this bug in Beta 4 and just confirmed it's also in Beta 6.  For example:  vsdiff ..\..\app.config Host01.exe.config      In this case, the "g" is lost in vsdiff processing of the command line args.  This problem does not occur for the first filename.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2047
  • Hero Points: 98
Re: vsdiff sometimes can't find second file on command line
« Reply #1 on: June 05, 2013, 07:53:05 pm »
Reproduced.  That's a weird one.  Thanks.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2047
  • Hero Points: 98
Re: vsdiff sometimes can't find second file on command line
« Reply #2 on: June 05, 2013, 09:07:14 pm »
Does it behave differently if you give the path to vsdiff?  Rather than relying on path searching, specify vsdiff with the absolute path.

twaithrb

  • Community Member
  • Posts: 28
  • Hero Points: 0
Re: vsdiff sometimes can't find second file on command line
« Reply #3 on: June 05, 2013, 11:01:18 pm »
Cool question!  When I supply the full path to vsdiff on the command line, the problem does not occur, neither in Beta4 nor Beta6.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2047
  • Hero Points: 98
Re: vsdiff sometimes can't find second file on command line
« Reply #4 on: June 06, 2013, 05:27:07 pm »
Fixed for the next beta.  Thanks for the report.