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: Sat, 06 Apr 2019 23:53:01 +0300 [thread overview]
Message-ID: <877ec6c0uq.fsf@mail.linkov.net> (raw)
In-Reply-To: <87r2ahornd.fsf@gmx.de> (Michael Albinus's message of "Fri, 05 Apr 2019 09:08:54 +0200")
>>> Some escape sequences are unhandled in shell mode.
>>> Most often they appear when running `apt install'
>>> that shows its progress bar that is supposed to stay
>>> on the same line, but spreads over several lines,
>>> so the output looks like a mess (where ^[7 and ^[8
>>> are escape sequences currently still unhandled):
>>
>> After more research, I found an interesting post
>> https://oremacs.com/2019/03/24/shell-apt/
>> that proposes a promising way to handle
>> these escape sequences.
>>
>> So maybe this should be customizable?
>
> 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
> 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?
next prev parent reply other threads:[~2019-04-06 20:53 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 [this message]
2019-04-07 8:46 ` Michael Albinus
2019-04-07 20:05 ` Juri Linkov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ec6c0uq.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).