Julien LOLLIVIER
Julien LOLLIVIER
Hi, While it seems very feasible, I currently don't think it's a good idea. This tool is supposed to be generic, hard coding special behavior specific to some commands does...
Thinking about a way to make `progress` able to deal with multiple files per command (and `/proc//cmdline` can probably help) but I can't find any good idea for commands like...
File order for `cp -R` and other recursive forms of coreutils commands is build with `readdir()` (coreutils source code, file savedir.c, function `savedirstream()`) and this function doesn't guarantee any ordering,...
@cheater The main issue here is the lack of ordering of `readdir()`. We have no guarantee the file list order will be the same as the one `cp` (for instance)...
What is already implemented is only related to the currently opened file. To get "how many bytes have been copied since the beginning", we need to know what is the...
Basically, the order is provided by the underlying filesystem(s) and some of them are quite complex and I'm pretty sure that a big re-indexing can happen in apparently basic use-cases....
At our level, we've no idea of what the FS is doing. A change at the other end of the disk, by another user, without any relation with our copy/move/whatever...
Feel free to experiment, of course. I will keep this subject on my list, too.
And what if destination folder was already here and is overwritten by the copy?
Added. I imagine that there's more aliases than these two, what are the other possible "g* commands"?