How recover file lost when Thunar crashed during cut-and-paste?

[MR ZenWiz]

On Sat, Jan 30, 2016 at 9:26 AM, Genghis Khan <genghiskhan at gmx.ca> wrote:
> This bug disturbs me, too.
>
> I agree that this report is not good for the reliability of
> Thunar; and yet, I do not see any good value in bashing the
> developers, directly or indirectly.
>
> I think that using the word remiss towards the developers is
> more than enough.
>
> A better manner to handle this issue is to subscribe to the
> relevant bug report, and petition the developers about this
> concern.
>

I am an old-time command line enthusiast, so bear this in mind.

When it comes to moving any kind of files, whether for backup,
relocation or pretty much any kind of large scale movement, I rely on
rsync rather than cp, mv, or Thunar.  It is safer and less prone to
failure, and it leaves behind whatever files you didn't finish copying
in hidden files with similar names for your own recovery or disposal
later.

Yes, it is not as convenient as mv (you have to go through and delete
the original files if your intent was to move them), or as
GUI-oriented as anything in Thunar, but it is like most of the
underlying Linux we all love - rock solid and reliable beyond compare.
It is also flexible enough to work across networks.

The maze of rsync options can be confusing, but the simplest form
which I regularly use is 'rsync -av --progress <src-list> <dest>.'
This preserves date-time stamps, links, ownerships and permissions.
The only real trick is mastering how to specify directories with or
without the trailing separator.

YMMV.
MR