From: Jack Hill <jackhill@jackhill.us>
To: Guix Devel <guix-devel@gnu.org>
Subject: Re: Guix search, colors and INSIDE_EMACS
Date: Tue, 11 Feb 2020 11:37:08 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.20.2002111128170.11123@marsh.hcoop.net> (raw)
In-Reply-To: <CAJ3okZ3h68nDHZQYA6tAX-+-0-JxaykcAheAWTXbkoOV=L8CAg@mail.gmail.com>
Hi Guix,
I've been trying to follow this discussion as I have observed problems
with the linking characters in eshell. However, it seems I am having
seeing different behavior than others. In both Emacs 26.3 and Emacs-next
27.0.50, running as `emacs -q`, INSIDE_EMACS is not being set in eshell
so, guix describe looks like
guix describe
]8;;file://lib-its13/var/guix/profiles/per-user/install/current-guix-66-link\Generation 66 Feb 07 2020 10:38:56]8;;\ (current)
guix 232f344
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: ]8;;https://git.savannah.gnu.org/cgit/guix.git/commit/?id=232f344f9b9dc775fe8f9c7db2e45ba20431b071\232f344f9b9dc775fe8f9c7db2e45ba20431b071]8;;\
In shell and term mode, INSIDE_EMACS is being set, and everything looks fine
(although without any highlighting).
Is something wrong with my emacs that INSIDE_EMACS is not being set?
Is there some other way that guix can detect if it is running from eshell?
Best,
Jack
next prev parent reply other threads:[~2020-02-11 16:37 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:23 Guix search, colors and INSIDE_EMACS Pierre Neidhardt
2020-02-04 16:12 ` Ricardo Wurmus
2020-02-04 16:37 ` Pierre Neidhardt
2020-02-04 16:51 ` zimoun
2020-02-04 19:16 ` Ricardo Wurmus
2020-02-04 19:18 ` Ricardo Wurmus
2020-02-06 9:51 ` Pierre Neidhardt
2020-02-13 9:30 ` zimoun
2020-02-13 13:41 ` Alex Griffin
2020-02-13 14:22 ` zimoun
2020-02-14 7:17 ` Pierre Neidhardt
2020-02-14 7:21 ` Pierre Neidhardt
2020-02-17 7:51 ` Pierre Neidhardt
2020-02-17 7:54 ` zimoun
2020-02-17 13:42 ` Pierre Neidhardt
2020-02-17 18:33 ` zimoun
2020-02-24 10:19 ` Pierre Neidhardt
2020-02-24 16:22 ` Ludovic Courtès
2020-02-24 16:44 ` Pierre Neidhardt
2020-02-24 17:11 ` zimoun
2020-02-24 20:54 ` Ludovic Courtès
2020-02-24 21:32 ` Pierre Neidhardt
2020-02-24 16:53 ` zimoun
2020-02-05 15:13 ` Ludovic Courtès
2020-02-06 9:56 ` Pierre Neidhardt
2020-02-07 21:33 ` Ludovic Courtès
2020-02-08 16:34 ` Pierre Neidhardt
2020-02-04 16:40 ` zimoun
2020-02-10 19:36 ` Pierre Neidhardt
2020-02-10 23:24 ` zimoun
2020-02-11 6:22 ` Pierre Neidhardt
2020-02-11 14:11 ` Ludovic Courtès
2020-02-11 14:19 ` Pierre Neidhardt
2020-02-11 15:14 ` zimoun
2020-02-11 16:37 ` Jack Hill [this message]
2020-02-11 18:09 ` zimoun
2020-02-11 19:04 ` Jack Hill
2020-02-12 13:39 ` Pierre Neidhardt
2020-02-12 16:30 ` zimoun
2020-02-13 9:35 ` zimoun
2020-02-24 16:18 ` Ludovic Courtès
2020-02-24 16:45 ` Pierre Neidhardt
2020-02-24 16:59 ` zimoun
2020-02-24 16:50 ` zimoun
2020-02-11 15:11 ` zimoun
2020-02-11 15:06 ` zimoun
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=alpine.DEB.2.20.2002111128170.11123@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=guix-devel@gnu.org \
/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).