From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] emacs: Enable 'guix-build-log-minor-mode' in shell buffers.
Date: Sun, 01 Nov 2015 18:46:59 +0100 [thread overview]
Message-ID: <87fv0p394c.fsf@gnu.org> (raw)
In-Reply-To: <871tcalqgg.fsf_-_@gmail.com> (Alex Kost's message of "Sat, 31 Oct 2015 23:42:55 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Not sure if it's really worth, but this can be done the same way as with
> enabling 'guix-devel-mode' (as in the attached patch). So it can be
> disabled by:
>
> (setq guix-build-log-minor-mode-activate nil)
OK.
> But then why don't we enable 'guix-prettify-mode' by default? As for
> me, I don't think all these features should be automatically enabled,
> dunno what is considered to be a good default: "full-featured" or "as
> simple as possible".
I’m mostly in favor of full-featured. The Emacs tradition is/was to
provide something that had to be explicitly configured to get the
features: in the old days, font-locking was disabled by default, and
Gnus would do absolutely nothing until you had spent a couple of days
configuring it.
However, given the wealth of features now provided by guix.el, I think
it’s best to enable most of them by default, at least those that are not
controversial. Otherwise, the risk is that people just won’t know about
them.
‘guix-build-log-minor-mode’ is clearly one of the things to enable by
default IMO. The situation is less clear for ‘guix-prettify-mode’
because it changes the behavior of Emacs in a way that could be
surprising to a newcomer.
WDYT?
> From 3991193fcc6700b1e198d5befcb6b1c651839ae0 Mon Sep 17 00:00:00 2001
> From: Alex Kost <alezost@gmail.com>
> Date: Sat, 31 Oct 2015 22:01:45 +0300
> Subject: [PATCH] emacs: Enable 'guix-build-log-minor-mode' in shell buffers.
>
> * emacs/guix-build-log.el (guix-build-log-minor-mode-activate): New variable.
> (guix-build-log-minor-mode-activate-maybe): New function.
> * emacs/guix-init.el: Add it to 'shell-mode-hook'.
> * doc/emacs.texi (Emacs Build Log): Mention it.
OK!
Ludo’.
next prev parent reply other threads:[~2015-11-01 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 20:33 [PATCH 2/3] emacs: Add key bindings for 'guix-build-log-minor-mode' Alex Kost
2015-10-30 16:51 ` Ludovic Courtès
2015-10-31 20:42 ` [PATCH] emacs: Enable 'guix-build-log-minor-mode' in shell buffers Alex Kost
2015-11-01 17:46 ` Ludovic Courtès [this message]
2015-11-02 13:01 ` Alex Kost
2015-11-02 14:14 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fv0p394c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.