rox with transmision bar ??

[Argolance]

...
Avec Rox, je ne suis parvenu à rien, désolé!

[fabrice_035]

Delete attachement, copy yourself the scripts

[Argolance]

Thanks.

your screenshot shows that you modified the script in a bad way

I copied/pasted the scripts given above as they are, then tested them with Rox but without success. Only after that, I modified the scripts following your advise to test cp in command line.This is what the picture shows.

So if I use the scripts you sent as compressed file above, I copy cp to /bin (where is the original cp, but what do I do with it? Rename as cp_original?), and rsync_gtk.sh to /usr/local/bin?

I will test this tomorow.
Good night.

[fabrice_035]

Thanks.

So if I use the scripts you sent as compressed file above, I copy cp to /bin (where is the original cp, but what do I do with it? Rename as cp_original?), and rsync_gtk.sh to /usr/local/bin?

Yeah that's right! So i you want test cp script without Rox, make this change in cp script

BEFORE

Code: Select all

# if it's ROX-filer caller
if   [ "$proc" = "ROX-Filer" ] ; then 

AFTER

Code: Select all

# if it's ROX-filer caller
proc="ROX-Filer"
if   [ "$proc" = "ROX-Filer" ] ; then 

Code: Select all

[Argolance]

Bonjour et merci,

So if I use the scripts you sent as compressed file above, I copy cp to /bin (where is the original cp, but what do I do with it? Rename as cp_original?), and rsync_gtk.sh to /usr/local/bin?

Yeah that's right!

Not quite Mate...

• - Your script calls "ori_cp", and not "cp_original"
  - As soon as cp is renamed (even as "ori_cp"), it is not possible anymore to (use the command cp to) copy rshync_gtk.sh to /usr/local/bin!

As simple user who tries to help and test your work, I was wondering if you might not give a more detailed and precise protocol to do it properly.
Why not a pet package with pinstall.sh and puninstall.sh files?

Furthermore, you were right: the modifications I previously made to get cp script work without Rox were wrong. Besides, even if I follow the letter, something goes wrong, with or without...

Cordialement.

[fabrice_035]

Hello,

I modified the scripts yesterday, everything is up to date and consistent with the file names, sorry for the inconvenience.
Regard

[Argolance]

Hello,
I copied/pasted the scripts given above (v1.2 - 20190306) as /bin/cp_ (temporarily) and as /usr/local/bin/rsync_gtk.sh, gave them permissions, renamed /bin/cp to /bin/cp_original then /bin/cp_ as /bin/cp.
So far so good?
Then, I opened an existing directory somewhere in my documents containing files, created a "Newdir", dragged and dropped some files from that directory to this subdirectory.
Rox window "Copy" opened.
***That's when things got complicated.***
Nothing happened.
Waited some time, tried to close the rebellious window... without success!
Tried the copy manipulation from beginning again.
And again... to be sure!
Mouse cursor began to have very curious behavior.
Memory overflowed so I could not do anything else than roughly shutdown computer, restart it.
Ô dear, not possible to restart.
Tried again... to be sure!
...
So I ran another session, checked my pupsave which was "clean", had the idea to edit it, deleted /bin/cp and renamed /bin/cp_original to /bin/cp and my computer started again.

Here I am, mate: hot as hell!

So what about the original cp command when used by other processes than Rox (question I already asked at the beginning of this thread)?
It would seem to be a problem at least...

Cordialement.

[fabrice_035]

Hello,
I copied/pasted the scripts given above (v1.2 - 20190306) as /bin/cp_ (temporarily) and as /usr/local/bin/rsync_gtk.sh, gave them permissions, renamed /bin/cp to /bin/cp_original then /bin/cp_ as/bin/ cp.
.

[edit] Argolance was right, update cp script

The first script must replace cp in /bin/ but before rename cp as cp_original
Of course many process (mostly scripts) use cp every time.
Your question: what happens when a program calls default cp command (which now is my script.) ? simply if it's not Rox-Filer which call, the script call /bin/cp_original (and passing the arguments)
On my side I don't find any problems.
Regard.

[Argolance]

Hello,
On my side: an image is better than long speeches...

Cordialement.

[fabrice_035]

Point excellent Mister Argolance. it's harder than expected to find all the situations when you replace the command cp. Strange my rox never user "--no-preserve=context,links"
I understood where the problem was.
I'll think about that later.
Regard.
[ EDIT ] Solved, waiting for testers...

[Argolance]

Bonjour,
Version 1.4 works great!
Thank you a lot.

A quick question: the progress bar appears when you copy large file(s). Now, what about copying a huge directory containing many small files? Isn't it precisely in this kind of situation (it can take time, especially when the destination is an external drive), that a global progress bar would be really welcome?

Cordialement.

[fabrice_035]

Hi,

Thanks again Mister Argolance, good teamwork

I don't know why ROX-Filer show progressbar when we choose multiple files and copy it but nothing when it is needed copying a huge directory .

The only way to improve this is to work on the ROX-Filer source code i think.

Regard

[MochiMoppel]

I don't know why ROX-Filer show progressbar when we choose multiple files and copy it but nothing when it is needed copying a huge directory

Because progressbar shows the no. of finished copies. When you copy 2 large files ROX-Filer will show an empty progressbar while the copy of the first file is in progress. After finishing the first file the progressbar immediately shows 50%.

I hope this explains why you don't see anything when you copy only a single file, no matter if it's big or small. ROX-Filer doesn't even bother to add a progressbar as a progressbar would jump from empty to 100%, followed by an immediate closure of the dialog.

[fabrice_035]

I don't know why ROX-Filer show progressbar when we choose multiple files and copy it but nothing when it is needed copying a huge directory

Because progressbar shows the no. of finished copies. When you copy 2 large files ROX-Filer will show an empty progressbar while the copy of the first file is in progress. After finishing the first file the progressbar immediately shows 50%.

I hope this explains why you don't see anything when you copy only 1 file, no matter if it's big or small.

The problem raised concerns the difference between copying multiple files and copying a folder that contains multiple files.
*In the first case : show progress bar
*second case : no progress bar visible

[MochiMoppel]

*second case : no progress bar visible

Technically a folder is also a file. If in my example the first huge file would be a folder containing multiple files, you would see 50% progress after the folder was copied. ROX thinks of items to copy, and in this case 2 items. Doesn't matter if the items are regular files, links or folders. In order to show progress of the files contained in the folder. ROX would have to analyze folder content before starting with the copy process. No idea why this isn't done. To keep it simple?

[Argolance]

Hello,
By quickly rereading the messages of this thread from the beginning, It seems that fabrice_035's work responds to this Semme's suggestion.
Moreover, Semme proposed a small (internationalized at least in French) "MiniCopier" program which is far from being without interest: it is indeed exactly what Rox should naturally do...

[EDIT]: Link to minicopier-0.5_all.pet package with menu desktop file and icon (java environment required).

Cordialement.

[Argolance]

Bonjour,
I thought this might be helpful:
How to show the transfer progress and speed when copying files with cp?
And especially this:

progress - Coreutils Progress Viewer Build Status
What is it?
This tool can be described as a Tiny, Dirty, Linux-and-OSX-Only C command that looks for coreutils basic commands (cp, mv, dd, tar, gzip/gunzip, cat, etc.) currently running on your system and displays the percentage of copied data. It can also show estimated time and throughput, and provides a "top-like" mode (monitoring).

Code: Select all

# ./progress --help
progress - Coreutils Viewer
---------------------
Shows progress on file manipulations (cp, mv, dd, ...)

Monitored commands (default):
cp mv dd tar cat rsync grep fgrep egrep cut sort md5sum sha1sum sha224sum sha256sum sha384sum sha512sum adb gzip gunzip bzip2 bunzip2 xz unxz lzma unlzma 7z 7za zcat bzcat lzcat split gpg 

Usage: ./progress [-qdwmM] [-W secs] [-c command] [-p pid]
  -q --quiet                   hides all messages
  -d --debug                   shows all warning/error messages
  -w --wait                    estimate I/O throughput and ETA (slower display)
  -W --wait-delay secs         wait 'secs' seconds for I/O estimation (implies -w, default=1.0)
  -m --monitor                 loop while monitored processes are still running
  -M --monitor-continuously    like monitor but never stop (similar to watch ./progress)
  -a --additional-command cmd  add additional command to default command list
  -c --command cmd             monitor only this command name (ex: firefox)
  -p --pid id                  monitor only this process ID (ex: `pidof firefox`)
  -i --ignore-file file        do not report process if using file
  -o --open-mode {r|w}         report only files opened for read or write
  -v --version                 show program version and exit
  -h --help                    display this help and exit

Multiple options allowed for: -a -c -p -i. Use PROGRESS_ARGS for permanent arguments.

Code: Select all

# watch progress -q

... See image below.

Source

Cordialement.

[fabrice_035]

Excellent discovery Mister Argolance. I can imagine a graphical user interface to do justice to this very good program. you can do that ?

[Argolance]

Bonjour,
@fabrice_035
When reporting this little amazing program, I didn't think to make any GUI (though it may be interesting indeed to create a daemon working in the background), but rather that it could be used to solve the question asked in this thread (and some others?). If the cp progress report could be displayed directly inside the rox copy window, it would be great!
There must be someone on this forum who knows how to do this, right?

Cordialement.

[fabrice_035]

Let's do as usual, wait for someone to do it.