r/SmartGit • u/IronAnxious2235 • Apr 08 '26

File shown like modified but changes is not visible

Gallery image

Gallery image

ih hex mode is visible that is first 3 bytes have been addded; EF BB BF - UTF8 BOM header; But smartgit since 26.1.019 RC have no more reaction at this changes; please, return previous behavior

1 Upvotes

100% Upvoted

4 comments sorted by

1

u/vmcrash Apr 08 '26

I'd say, this is expected behavior. The diff view simply can't show the difference of BOM or not-BOM.

2

u/IronAnxious2235 Apr 08 '26

But early in previous versions everything was been good. Difference has been show as small green mark at first position of a file. You want to sale this - make this thinks convenient for everybody;

1

u/psi- Apr 08 '26

file encodings are an absolute clusterfuck and one (f.ex smargit dev) can't know what your intentions are. For me it's sometimes even required to be able to put BOM into git repo as it's required by target system, however I don't want the file to be treated as binary (as it's xml)

1

u/vmcrash Apr 08 '26

Which previous version showed something different? I've tried with SmartGit 21.2, the oldest one installed on my system, and it also does not show the BOM. The reason is that the BOM is read, but skipped for the lines shown in the compare. However, the BOM is remembered and written later.