unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Joshua Branson <jbranso@dismail.de>
To: help-guix@gnu.org
Subject: Re: Guix does not find packages
Date: Thu, 20 Feb 2020 09:49:14 -0500	[thread overview]
Message-ID: <86wo8hxqj9.fsf@dismail.de> (raw)
In-Reply-To: <875zg2fwn7.fsf@nckx> (Tobias Geerinckx-Rice's message of "Wed, 19 Feb 2020 16:02:20 +0100")

Tobias Geerinckx-Rice <me@tobias.gr> writes:

> Zelphir Kaltstahl 写道:
>> And then there is the strange issue, that I cannot install font
>> packages:
>>
>> `guix package -i font-fira-code font-fire-mono font-fire-sans`
>>
>> Gives:
>>
>> `guix package: error: font-fire-mono: unknown package`
>
> This is just a typo.  Correct it and try again ;-)
>
>> Is my Guix installation buggy? I never did anything weird to it,
>> only
>> ever used the Guix CLI commands to interact with it.
>
> No.  It was a deliberate decision to make ‘guix search’/‘guix package
> -s’ show only the ‘top’ result when stdout is a TTY.  I don't like it
> either.  The argument was that packages are sorted with the most
> relevant one at the top, which would scroll out of view.

Oh. Thanks for explaining that.

>
> I *still* think we should either do nothing, or call $PAGER
> automatically when stdout is a TTY.
>
> Kind regards,
>
> T G-R
>

-- 
Joshua Branson
Sent from Emacs and Gnus

      parent reply	other threads:[~2020-02-20 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 14:38 Guix does not find packages Zelphir Kaltstahl
2020-02-19 14:58 ` John Soo
2020-02-19 15:45   ` Zelphir Kaltstahl
2020-02-19 15:00 ` Joshua Branson
2020-02-19 15:02 ` Tobias Geerinckx-Rice
2020-02-19 15:06   ` John Soo
2020-02-19 15:38   ` Ricardo Wurmus
2020-04-23 20:07     ` Ludovic Courtès
2020-02-19 15:41   ` zimoun
2020-02-20 15:00     ` Pierre Neidhardt
2020-02-20 14:49   ` Joshua Branson [this message]

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=86wo8hxqj9.fsf@dismail.de \
    --to=jbranso@dismail.de \
    --cc=help-guix@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.
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).