SlickEdit Community

Archived Beta Discussions => SlickEdit 201x Beta Discussions => SlickEdit 2013 v18 beta => Topic started by: twaithrb on June 05, 2013, 05:48:38 PM

Title: vsdiff sometimes can't find second file on command line
Post by: twaithrb 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.

Title: Re: vsdiff sometimes can't find second file on command line
Post by: Dan on June 05, 2013, 07:53:05 PM

Reproduced.  That's a weird one.  Thanks.

Title: Re: vsdiff sometimes can't find second file on command line
Post by: Dan 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.

Title: Re: vsdiff sometimes can't find second file on command line
Post by: twaithrb 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.

Title: Re: vsdiff sometimes can't find second file on command line
Post by: Dan on June 06, 2013, 05:27:07 PM

Fixed for the next beta.  Thanks for the report.