From: excalamus--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 51454@debbugs.gnu.org
Subject: bug#51454: Progress bar in Org source blocks
Date: Thu, 28 Oct 2021 04:10:11 +0200 (CEST) [thread overview]
Message-ID: <Mn3eLkd--3-2@tutanota.com> (raw)
I'm trying to document my work with Guix using Emacs Org. If I run a shell/sh/bash source block in org-mode, the result has control characters in it.
To reproduce, open a clean instance of Emacs with emacs -q, switch to the scratch buffer and insert:
;; eval this first so that source blocks can run sh
(org-babel-do-load-languages
'org-babel-load-languages
'((shell . t)))
#+begin_src sh :results output :session test
guix package -u
#+end_src
#+RESULTS:
: guix package: ^[[1;35mwarning: ^[[0mnothing to do
Switch to org-mode, eval the lisp, and C-c C-c the source block. If your system is like mine, you'll see control non-printable characters.
When I check how org sees the shell, I get:
#+begin_src sh :results output :session test
echo $TERM
#+end_src
#+RESULTS:
: dumb
I've tried renaming .bashrc and .bash_profile to .bashrc.old and .bash_profile.old, starting a new shell and running through the steps above. The result is the same.
Thoughts and suggestions?
next reply other threads:[~2021-10-29 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 2:10 excalamus--- via Bug reports for GNU Guix [this message]
2021-10-29 12:51 ` bug#51454: Progress bar in Org source blocks 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
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=Mn3eLkd--3-2@tutanota.com \
--to=bug-guix@gnu.org \
--cc=51454@debbugs.gnu.org \
--cc=excalamus@tutanota.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).