From: excalamus--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 51454 <51454@debbugs.gnu.org>
Subject: bug#51454: Progress bar in Org source blocks
Date: Wed, 3 Nov 2021 18:05:48 +0100 (CET) [thread overview]
Message-ID: <MnakshN--3-2@tutanota.com> (raw)
In-Reply-To: <CAJ3okZ3jfQLaicFzEQd=ia+XYqS+HM1ZrO=QamMrcPdTHHpQhA@mail.gmail.com>
> I miss what you would like or what you are expecting.
>
My goal has been to clean up the guix command output as seen in an org-babel results block. I'm blogging about Guix using org-babel and Org's export functionality. I want the shell output as seen in the final html to be a reasonable approximation of the shell output a user would see if the command were run in something like xterm. Based on feedback from people in the Org community, I thought there might be a way to toggle off certain characters.
> And I do not think it is an issue about Guix. Instead, it is an issue about
> dealing with outputs and Org-mode (Babel).
>
I agree that handling this in org makes sense. When I asked the Org people, they had said it was a Guix issue. And with what we found with NO_COLOR, fair enough. You also raise a good point, however, that the characters originate upstream. Anything Guix might do would be a work around and work arounds are probably best handled in Emacs.
> for instance, something along these lines...
>
Thank you for the example. I was unaware of the Emacs function ansi-color-apply-on-region. The rest can probably be handled with replace-match.
I appreciate all your help. Thank you, Simon!
next prev parent reply other threads:[~2021-11-03 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 2:10 bug#51454: Progress bar in Org source blocks excalamus--- via Bug reports for GNU Guix
2021-10-29 12:51 ` zimoun
2021-10-30 4:55 ` excalamus--- via Bug reports for GNU Guix
2021-10-30 16:43 ` zimoun
2021-11-01 2:03 ` excalamus--- via Bug reports for GNU Guix
2021-11-03 14:14 ` zimoun
2021-11-03 17:05 ` excalamus--- via Bug reports for GNU Guix [this message]
2021-11-03 17:52 ` zimoun
2021-11-04 0:43 ` excalamus--- via Bug reports for GNU Guix
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MnakshN--3-2@tutanota.com \
--to=bug-guix@gnu.org \
--cc=51454@debbugs.gnu.org \
--cc=excalamus@tutanota.com \
--cc=zimon.toutoune@gmail.com \
/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/guix.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).