Author Topic: DiffZilla - diffing garbage at end of temp file  (Read 1296 times)

b

  • Senior Community Member
  • Posts: 320
  • Hero Points: 26
DiffZilla - diffing garbage at end of temp file
« on: April 30, 2019, 09:39:41 pm »
I've been using the feature to compare two different buffers.   Particularly, since we use AccuRev (and SE can't support it), from AccuRev I open a version, which saves a temp file buffer and passes the temp file to SE.   Then I can do a Ctrl-= and select my copy of the open file (in a buffer), against the temp file buffer.

I've tried this on a few files, and have been seeing that SE appears to be either adding, or somehow not catching the end of the temp file and adding garbage to the diff.   From SE, if I open the file's location and then open the temp file with Notepad, it shows exactly what I expect (with the correctly terminated EOF of the temp file).

Code: [Select]
SlickEdit Pro 2018 (v23.0.1.2 64-bit)

Serial number: FE10296
Licensed number of users: Single user
License file: C:\ProgramData\slickedit\23\slickedit.lic

Build Date: April 24, 2019
Emulation: Vim

OS: Windows 10 x64
OS Version: 10.00.0 
Memory: 57% Load, 9407MB/16265MB Physical, 13002MB/18697MB Page File, 41575MB/134217727MB Virtual
Shell Information: C:\WINDOWS\system32\cmd.exe /q
Screen Size: 1920 x 1040, 1920 x 1080, 1200 x 1920

Project Type: Microsoft Visual Studio Visual C++
Language: .tmp (Plain Text)
Encoding: Automatic

Installation Directory: C:\Program Files\SlickEdit Pro 23.0.1\ (non-removable drive,NTFS,27589MB free)
Configuration Directory: C:\Users\bkurle\Work Folders\Documents\My SlickEdit Config\23.0.1\ (non-removable drive,NTFS,27589MB free)

Hotfixes:
C:\Users\bkurle\Work Folders\Documents\My SlickEdit Config\23.0.1\hotfixes\hotfix_se2301_4_cumulative.zip (Revision: 4)



Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5779
  • Hero Points: 461
Re: DiffZilla - diffing garbage at end of temp file
« Reply #1 on: May 06, 2019, 09:37:53 pm »
Is there an EOF character which is supposed to indicate that file is shorter than the actual file size?

There is a "Truncate file at EOF" option which is off by default. Tools>Options>File Options>Load
« Last Edit: May 06, 2019, 09:42:56 pm by Clark »

b

  • Senior Community Member
  • Posts: 320
  • Hero Points: 26
Re: DiffZilla - diffing garbage at end of temp file
« Reply #2 on: May 07, 2019, 09:11:43 pm »
Since this is a Windows generated temporary file, I don't believe so (in so much as when I look at the temp file, it appears to be correct (EOF location and file size look correct).

I will try to run a few more tests when I use it again.

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3254
  • Hero Points: 462
Re: DiffZilla - diffing garbage at end of temp file
« Reply #3 on: May 08, 2019, 03:38:27 pm »
Try scrolling up and down in the Diff window to verify that this is not just a drawing anomoly.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2560
  • Hero Points: 141
Re: DiffZilla - diffing garbage at end of temp file
« Reply #4 on: May 09, 2019, 02:24:02 pm »
What happens if you shut off Source Diff?

b

  • Senior Community Member
  • Posts: 320
  • Hero Points: 26
Re: DiffZilla - diffing garbage at end of temp file
« Reply #5 on: May 09, 2019, 10:54:18 pm »
Try scrolling up and down in the Diff window to verify that this is not just a drawing anomoly.


At the time, I had.   Since its a vi emulation, I saw the obligatory ~ on each of the line when the end of file was encountered.   

b

  • Senior Community Member
  • Posts: 320
  • Hero Points: 26
Re: DiffZilla - diffing garbage at end of temp file
« Reply #6 on: May 09, 2019, 10:57:13 pm »
What happens if you shut off Source Diff?

Now that I've had a moment to go back and trouble shoot this, I'm not reproducing it.   At the time it was a great annoyance, but now that a few days have passed (and SE has been closed and reopened several times and several project switches), I've not yet reproduced it as I had before (which at the time I could on demand).    So, I'm not sure what happened.    I'll keep an eye on it and reopen this thread with more info when I see it again.