folder name case difference

[hartungr]

I'm comparing folders on 2 Linux systems, and have several instances where a folder name is all uppercase on one but all lowercase on other.

ie
synth/scripts/RCS vs synth/scripts/rcs

Is there an alignment override reg exp I can define on the Misc tab to get these to be treated as matching? Or a general session setting to do the same?

Using both Win and Linux versions to access the Linux folders, same non-alignment with either version. 3.1.10 (build 11626)

[Aaron]

Hello,

Beyond Compare automatically tries to follow how the file system would treat your directories. On Windows, case is not sensitive, so those two folders would align. On Linux, however, case is important, so the folders would not align (if they were two local folders on a local Linux machine, that would be the correct behavior). This is not configurable in the current version of Beyond Compare.

How are you connecting to the 2 Linux systems? We do have one configuration that may help you. If you are connecting with FTP, you can toggle how FTP's treat case sensitivity under the Tools menu -> FTP Profiles. Pick a specific profile or change the default, and go to the General tab. Disable "Filenames are case sensitive." How does that work for you?

[hartungr]

Thanks for the reply, Aaron.

Changing the FTP profile to disable "filenames are case sensitive" produces no change. Both folders and filenames that differ only in case are still non-aligned. (This is from Windows via SFTP to Linux)

And there is no alignment override regular expression that can workaround this?

[Chris]

Hi Bob,

It looks like the "filenames are case sensitive" setting only works when comparing a local folder to an SFTP server. For SFTP to SFTP comparisons it doesn't work in the current release of BC3.

If you have BC3 Pro it is possible to ignore character case using a regular expression. Select "Session > Session Settings". Go to the "Misc" tab. Create a new alignment override.

Align left file: (.*)
with right file: (?i)$1

Check regular expression.

The .* matches the entire file name, putting it in parenthesis saves it as the variable $1. The expression (?i) means ignore character case.

[Chris]

I took another look at this, setting "filenames are case sensitive" might actually work. Does it help if you uncheck this setting in the FTP profile, then restart BC and open the comparison again?

[beelsr]

it would be nice if this functionality was added to BC3.

I'm in the process of converting files from a NetWare server to a Linux server. On NW, the folders are all uppercase, in linux they need to be lowercase. Running BC from a workstation treats them equivalent and copies fun ,it's just s...l...o...w... because of 2 network trips for the data and local processing on my PC. I can run BC on the linux destination and pull the files directly but with 130GB and hundreds of folders, the case differentiation kills this....

The little regex a couple posts ago doesn't work... :-(

Please, add a check box item in session setting right next to "Compare filename case"...

[Aaron]

Hello,

With Chris' last post, the File Names are Case Sensitive option should work, but you may need to fully restart BC3 to get the setting to apply. If you disable the FTP Profile setting on both profiles, and then fully restart BC3, do you still have trouble aligning your data? Are you using the latest version of BC3 (3.2.4)?

[beelsr]

Hi Aaron, thanks for the reply. Unfortunately, it doesn't work.

I'm not using ftp to connect to the remote server, if that matters, though I did disable the setting in the default profile...

[Aaron]

Hello,

Thanks for the info. You'll need to connect via FTP to use the ftp profile option. Otherwise BC3 detects the current filesystem options. Since Linux is case sensitive, your folders will also be case sensitive.

[beelsr]

fair enough. i hereby reiterate my point of post #6. please add an "ignore filename case" setting. it would really, really help....

[Aaron]

Sure, beelsr.

I have a couple of quick questions. On your Netware device outside of BC3, are you able to have multiple files with the same name and different case? Is the Netware normally case sensitive or case insensitive? Does it change the character case on its own and what action causes that?

[beelsr]

Hi Aaron...

No, netware follows dos/windows case (in)sensitivity rules. AUTOEXEC.NCF is the same as autoexec.ncf is the same as AuToeXeC.NCF, etc... It doesn't change case on filenames at all and accepts them just as Windows does.

FWIW, I've run into this same issue in doing Windows to Linux conversions as well. So, the easy answer is forget I mentioned NetWare and just think about Windows... :-)

Sure, beelsr.

I have a couple of quick questions. On your Netware device outside of BC3, are you able to have multiple files with the same name and different case? Is the Netware normally case sensitive or case insensitive? Does it change the character case on its own and what action causes that?

[Zoë]

BC should actually align case insensitively if either file system is case insensitive. On Linux we detect that on a directory-by-directory basis, but we might not have covered yours. FAT32 and NTFS will both be aligned that way for example. Do you know what the filesystem the Netware server is using is (how it's mounted on Linux)?

[beelsr]

Hmmm, NetWare's filesystem is NSS and it's mounted on the linux servers via ncpmount.