From: excalamus--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 51454@debbugs.gnu.org
Subject: bug#51454: Progress bar in Org source blocks
Date: Sat, 30 Oct 2021 06:55:05 +0200 (CEST) [thread overview]
Message-ID: <MnEYGl5--3-2@tutanota.com> (raw)
In-Reply-To: <CAJ3okZ1P9LL1t5QzUQcvCtq3QYFT=wzoxbiNReM5TeP-AB8WKQ@mail.gmail.com>
> try the environment variable INSIDE_EMACS with turns off
> some fancy shell things.
>
This is a good suggestion. Maybe I'm misunderstanding how INSIDE_EMACS works. The docs say:
"Emacs sets the environment variable INSIDE_EMACS in thesubshell to ‘version,comint’, where version is theEmacs version (e.g., ‘24.1’). Programs can check this variableto determine whether they are running inside an Emacs subshell."
https://www.gnu.org/software/emacs/manual/html_node/emacs/Interactive-Shell.html
When I check it in a session set up as described above, I get the Emacs version:
#+begin_src sh :results output :session unset
echo $INSIDE_EMACS
#+end_src
#+RESULTS:
:
: 27.2,comint
I understand this to mean that INSIDE_EMACS *is* being set and that it's the guix command's responsibility to do something with it (if it wants to).
If instead I set INSIDE_EMACS to something falsey (e.g. 1) and run through things, I see the same result with color and control characters.
next prev parent reply other threads:[~2021-10-30 4:56 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 [this message]
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=MnEYGl5--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).