From: Juri Linkov <juri@linkov.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 35129@debbugs.gnu.org
Subject: bug#35129: Unsupported escape sequences for progress in shell
Date: Sun, 07 Apr 2019 23:05:19 +0300 [thread overview]
Message-ID: <87y34l3ei0.fsf@mail.linkov.net> (raw)
In-Reply-To: <87r2aei4ok.fsf@gmx.de> (Michael Albinus's message of "Sun, 07 Apr 2019 10:46:03 +0200")
>>> Looks interesting. However, we have `progress-reporter'. The code from
>>> above shall be made available via this.
>>
>> I'm not sure if we can provide min-value/max-value for
>> make-progress-reporter. If not, then it uses spinning/pulsing.
>> It seems progress-reporter doesn't support arbitrary strings
>> such as that come from underlying process like ^[7Progress: [ 0%]^[8
>
> progress-reporter should be improved to accept also strings like "45%"
> to be displayed literally.
Another problem is that there is no clear moment to start/stop
progress-reporter with calls to make-progress-reporter and
progress-reporter-done.
>>> This would also improve Tramp; there are requests to integrate the
>>> progress reporter from external commands.
>>
>> Could you show an example of a progress reporter from an external command.
>> Do they use arbitrary strings?
>
> Some scp or pscp versions do it. For example:
>
> $ pscp -v localhost:/net/ford/Multimedia/Eigene\ Videos/Videos/20150829_145255.mp4 /tmp/foo
> [...]
> foo | 203369 kB | 5810.6 kB/s | ETA: 00:00:00 | 84%
Progress on copying large files would be needed for local file operations
as well.
next prev parent reply other threads:[~2019-04-07 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 20:27 bug#35129: Unsupported escape sequences for progress in shell Juri Linkov
2019-04-04 20:36 ` Juri Linkov
2019-04-05 7:08 ` Michael Albinus
2019-04-06 20:53 ` Juri Linkov
2019-04-07 8:46 ` Michael Albinus
2019-04-07 20:05 ` Juri Linkov [this message]
2019-04-08 7:36 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y34l3ei0.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=35129@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.