Thanks for your contribution!
That said, I think I might have caused some misunderstandings here. The
reason I used asciinema.org was just to animate what the console output
originally was, and the service by itself doesn't have the ability to
automatically substitute escape sequences or whatsoever. What I actually
did was just substitute all dots followed by '[', ']', '(' or ')' to the
ASCII ESC (0x1b, ' ') character, a method that could have false positives.
Since the patch I mentioned also adds the '-r' flag which reverts its
escape filtering feature, you can try it out with `xl console -r <Domain
ID>` (although highly not recommended).
I'll submit the correction PR when I get to have some free time for it. I
apologize for not having made this clear. Meanwhile if you'd like to do it
instead -- since you're also the author of the article -- then I'd
appreciate it ;)
On Sat, Oct 19, 2019, 13:42 <[email protected]> wrote:
> On Thu, Oct 17, 2019 at 01:24:00PM -0700, Jin-oh Kang wrote:
> >The escape sequence crippling is caused by
> https://github.com/QubesOS/qubes-vmm-xen/blob/xen-4.8/patch-tools-xenconsole-replace-ESC-char-on-xenconsole-outp.patch
> , which is reasonable given the Qubes security model.
> >
> >For interactive console you could use `qvm-console-dispvm <vmname>`
> provided by the qubes-core-admin package.
>
> I wish I had seen that tool earlier! Here's a PR for the community docs:
>
> https://github.com/Qubes-Community/Contents/pull/74
>
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/CAMnQwqVkSqSt-xbo7Yr82d4Pcz-ehw1ngNuYf_fi804kQBR11A%40mail.gmail.com.
