From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Guix search, colors and INSIDE_EMACS
Date: Tue, 04 Feb 2020 17:12:12 +0100 [thread overview]
Message-ID: <87tv46qqlf.fsf@elephly.net> (raw)
In-Reply-To: <87blqeml4w.fsf@ambrevar.xyz>
Hi Pierre,
> - Rename it to GUIX_INSIDE_EMACS?
> - Document the existence of INSIDE_EMACS.
The variable is set by Emacs. As an Emacs feature we should not
document it in Guix, nor should we rename it to GUIX_INSIDE_EMACS.
> - Leave colors on when inside Emacs.
Wouldn’t this mess with font lock in Emacs modes such as M-x shell? My
colour theme has no place for a garish green :)
For prettier colours in Emacs we already have things like
guix-build-log-mode.
> - Disable the pager hint and display all research result when inside
> Emacs.
Isn’t it considered best practise to set PAGER=cat when using Emacs as a
shell? That’s what I do to show man pages (when I’m not using M-x
woman) or to have “git log” do the right thing.
--
Ricardo
next prev parent reply other threads:[~2020-02-04 16:12 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 [this message]
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
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=87tv46qqlf.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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).