From: Ricardo Wurmus <rekado@elephly.net>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: gwl-devel@gnu.org
Subject: Re: Getting started with GWL 0.3.0
Date: Tue, 23 Mar 2021 14:16:48 +0100 [thread overview]
Message-ID: <874kh2vwlb.fsf@elephly.net> (raw)
In-Reply-To: <m17dlykoyh.fsf@ordinateur-de-catherine--konrad.home>
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
> In the long run, maybe a command spell-checker would be a nice way out.
> Some piece of software that decides, based on my command history,
> whether a command I type is more likely a typo or the intention to run
> some exotic software.
This would need more work to allow replacement of Guix commands with an
extension. For example, I may want to use an extension that replaces
“guix deploy” with a variant that can deploy to AWS, falling back to the
default “guix deploy” for all other deployments.
We should not prevent this use case, so at the very least this needs to
be configurable (though I’d be happier if we could come up with a
configuration-free solution).
A configuration-free alternative could be “guix ext pull” to explicitly
select the extension named “pull”. There can be no conflicts with this
scheme, but it’s more work to type.
--
Ricardo
next prev parent reply other threads:[~2021-03-23 13:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 10:32 Getting started with GWL 0.3.0 Konrad Hinsen
2021-03-22 11:03 ` zimoun
2021-03-22 13:04 ` Konrad Hinsen
2021-03-22 13:51 ` zimoun
2021-03-22 15:07 ` Konrad Hinsen
2021-03-22 18:16 ` zimoun
2021-03-23 12:57 ` Konrad Hinsen
2021-03-23 13:16 ` Ricardo Wurmus [this message]
2021-03-23 13:24 ` Roel Janssen
2021-03-23 20:16 ` zimoun
2021-03-24 10:08 ` Konrad Hinsen
2021-03-24 10:44 ` zimoun
2021-03-23 15:51 ` Konrad Hinsen
2021-03-23 17:34 ` Ricardo Wurmus
2021-03-23 19:30 ` Roel Janssen
2021-03-23 20:14 ` Ricardo Wurmus
2021-03-23 20:30 ` Roel Janssen
2021-03-26 21:01 ` Ricardo Wurmus
2021-04-30 21:50 ` Ricardo Wurmus
2021-03-24 9:52 ` Konrad Hinsen
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://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kh2vwlb.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.org \
--cc=konrad.hinsen@fastmail.net \
/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.
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).