You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Say you have a file foo/myfile and a file bar/myfile, which are hard linked to the same inode (e.g. with the command ln foo/myfile bar.). If you mv foo/myfile bar/myfile or cp foo/myfile bar/myfile in a terminal, you get an error message mv: 'foo/myfile' and 'bar/myfile' are the same file, and similarly for the copy.
SpaceFM, either when dragging myfile from foo/ to bar/ (for move, or with [Ctrl] down for copy), or via the clipboard with [Ctrl]+x or [Ctrl]+c followed by [Ctrl]+v, pops up a confirmation dialog, stating that both files are the same size and timestamp, but does not mention they are the same file. If you confirm the move or copy, both foo/myfile and bar/myfile are truncated to 0 bytes.
Note: the tests were performed on a tmpfs file system.
The text was updated successfully, but these errors were encountered:
Say you have a file foo/myfile and a file bar/myfile, which are hard linked to the same inode (e.g. with the command
ln foo/myfile bar.
). If youmv foo/myfile bar/myfile
orcp foo/myfile bar/myfile
in a terminal, you get an error messagemv: 'foo/myfile' and 'bar/myfile' are the same file
, and similarly for the copy.SpaceFM, either when dragging myfile from foo/ to bar/ (for move, or with [Ctrl] down for copy), or via the clipboard with [Ctrl]+x or [Ctrl]+c followed by [Ctrl]+v, pops up a confirmation dialog, stating that both files are the same size and timestamp, but does not mention they are the same file. If you confirm the move or copy, both foo/myfile and bar/myfile are truncated to 0 bytes.
Note: the tests were performed on a tmpfs file system.
The text was updated successfully, but these errors were encountered: