Compare Files and Directory "Case sensitive"

[MyUser]

Hello :-)

How can I compare directories and/or files with not exact name, for example
comparing the two directories "C:\FileS\" with "D:\Files\".

But BC shows no difference...

My Session Setting:
Compare filename case: checked

I use Version 3.1.6 Build 10721.

Tnx a lot
:-)

[Aaron]

Hello,

Compare filename case currently only supports file names, and not folder names. If the files align, and the case is different, it will then show as a difference.

If folders are detected as having different names (on Linux systems, case is considered an Important difference), then the two folders don't align and are treated as different names; since on a Linux system you can have Files and FileS in the same directory.

[hamigaki]

BC2 supported to detect Folder Case sensitive. then we have confuse the different behavior.

Do you have the plan for supporting Folder Case sensitive option on BC3 ?

[Aaron]

Hello Hamigaki,

This is now controlled by the host OS. If you are running on Windows, Windows explorer considers the name the same; on Linux they are considered different.

Could you go into more detail on your workflow and how foldername case comparison helps you specifically?

[Pete]

Could you go into more detail on your workflow and how foldername case comparison helps you specifically?
Yes, because I change the case of some words in folder names. Because BC ignores case, it doesn't backup these new folder names during syncing, thus I lose all my effort when I restore from backup.

It's not a matter of whether Windows cares about case. It's a matter of BC users caring about case, and isn't this more important? Frankly I don't understand all the resistance to fixing this.

[Craig]

Frankly I don't understand all the resistance to fixing this.

Pete,

I already gave the reasons for the "resistance" in the Comparing filename case feedback (http://www.scootersoftware.com/vbulletin/showthread.php?t=3947) thread. To reiterate, BC compares files within folders, not the folders themselves, and adding such support will be a substantial change that may introduce subtle bugs. I completely agree that it's better for the "Compare filename case" option to affect folders as well, and I would like to do it, but there are other enhancements that have significantly higher priority right now.

Aaron was just asking for additional details to flesh out the enhancement request with additional use cases, which may boost its priority.

[hamigaki]

We have been using BeyondCompare with Version control system.

Next following is our work flow.

1. Make diff report between current source tree and new given source tree.
2. Check file and folder case sentive.
3. If we found the diffarent Case sensitive. we had to adjust case of givin source code.
4. do imoprt oparation.

If we cannot found folder case sensitive, Version control system recoginize the folder as new element...

We strong want to make correct diff information for report only...

now We need to both (bc2,3) version for our oparation step...

[chrisjj]

> This is now controlled by the host OS.

OOI, what about snapshots? Do they record the host OS?

[Aaron]

The Linux version currently does not consider folder case for snapshots. It is on our wishlist to add this functionality.

So whether you transfer the snapshot from linux or to linux, it does not treat case as important in the current version.

[chrisjj]

Um, is that a yes or a no, please?

[Aaron]

I'm not sure. If it is or isn't, it currently does not have an impact on how the snapshot is presented and is something we would like to handle in a future version. If the information is recorded, how would you expect it to be handled?

[chrisjj]

> I'm not sure.

OK, thanks.

> If it is or isn't, it currently does not have an impact on how the snapshot is
> presented

Good!

> and is something we would like to handle in a future version.

Hmm...

> If the information is recorded, how would you expect it to be handled?

With care! :) I don't want hidden properties varying the BC interpretation of an ostensibly WYSIWYG record.

[Craig]

Um, is that a yes or a no, please?

No, snapshots do not currently record the host OS. They are always considered case-insensitive.

[chrisjj]

> No, snapshots do not currently record the host OS.

Thanks.

> They are always considered case-insensitive.

I don't understand how a document can be case insensitive. Is this to say any comparision with a shapshot is case insensitive? Even on an OS which is case sensitive?

[Craig]

Yes. Comparing against a snapshot is effectively the same as comparing against a directory on a FAT drive. The alignment will be case-insensitive. If you save a snapshot of a directory with files that differ only in case the snapshot itself will store the files properly, but it will only show one of the files when you load it.

[chrisjj]

> If you save a snapshot of a directory with files that differ only in case the
> snapshot itself will store the files properly,

I assume that's "...will store all files".

> but it will only show one of the files when you load it.

Well, that could definitely explain some mystery missing files here!!

How can I see these snapshot-stored files that are hidden when loaded in BC? The .bcss is otherwise illegible to me.

[Craig]

We've already cut-off for 3.1.7, but this will be fixed in the release following it. You can contact support@scootersoftware.com to get a pre-release that will load them correctly. If you wanted to see them otherwise you'd need to write a program to parse the .bcss file to get the data out. I'm happy to share the format, but it's a compressed binary format, so it's not trivial.

[chrisjj]

> this will be fixed in the release following it.

Thanks.

> If you wanted to see them otherwise you'd need to write a program to parse
> the .bcss file to get the data out.

I'll leave it to the experts :)