Dotfiles won't copy/move? Just...hangs?

[mpwilson]

So, I'm running 3133 on windows 10 (and 11) and have an issue where any filename that begins with a "."  (\users\foo\.frob) won't copy or move.  When MC gets to that file (whether it's the only one or in the midst of a queue) it simply stops as if it's about to copy it.

Only skipping the file will allow the process to continue.

Is there a setting I'm missing or is there something clever in the globbing system?

[Mathias (Author)]

Normal local NTFS filesystem ? or remote into a linux ?
Any error in the logs (ctrl+L , FileOperation log  )

Something special with the file ? does it have readonly or system attributes ?

If I create a file call ".file" I have no issue with copy/move it..

[mpwilson]

Sorry about the response lag.  I've narrowed this down a bit more meaningfully, though I've got a lot of test cases yet to go through.

I didn't realize how narrow a niche my use case really is.

The most reliable case thusfar is:

From: Windows local machine
To:     Linux remote machine, file already exists in destination.

Attempting to update the remote file reliably cause it to hang as described.  I WILL get an overwrite confirmation dialog if appropriate.  But "overwrite" will just close the dialog and put me back in to the individual file copy dialog. 

Elapsed time will continue to update and I can hit "skip" to move past that singular file.

Windows -> Linux (remote) new file: works
Linux (remote) -> Windows new file: works
Local new/overwrite:  Works.

Here's the options on a 3 file copy and the queue shot, just in case.

Weird stuff.

[Mathias (Author)]

Thanks for the information.. I will take a look.

I have not checked yet But I suspect the error is because of some workaround that MC has for the "hidden" file attributes and linux.
Linux does not have that file attribute, but on Linux a file is "hidden" if it begins with dot "."
So Samba (the thing on linux that make file sharing on Linux windows compatible) then say that the file has hidden attribute set since it is.
and that causes some combability issue. since you can't remove or set that attribute since it is based on filename.. so MC has some workaround for "." files and Linux.
So i maybe something might be wrong with the logic around that.