From: P via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
Joshua Branson <jbranso@dismail.de>
Subject: Re: fc-cache -f --> fc-cache -fv in the manual
Date: Tue, 10 Sep 2019 22:56:17 +0000 [thread overview]
Message-ID: <0Ka_5Nq1eZAuRrWUl5Gq8NioBvoc2FEYyTAnt-C0XAd_QvYSI1TjIxzKFzmX0D_nAMRpGmalPDhUx6RkQLeCNMjyD8EsYawwcChhzK7T-h4=@protonmail.com> (raw)
In-Reply-To: <20190910193214.00494e59@scratchpost.org>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, September 10, 2019 5:32 PM, Danny Milosavljevic <dannym@scratchpost.org> wrote:
> Hi T G-R,
>
> On Tue, 10 Sep 2019 19:00:41 +0200
> Tobias Geerinckx-Rice me@tobias.gr wrote:
>
> > > ran the command "fc-cache -f". It did successfully run, but I
> > > did not
> > > see any indication that it did anything. So I ran it
> > > repeatedly.
> >
> > Such is the Unix way. You're supposed to feel the 0 in the air,
> > or something.
>
> To be fair, you can set up the prompt so you can see the status code each time.
>
> I have in my ~/.bashrc:
>
> export PS1='${?#0} \u@\h \w\$ '
>
> That's a lot less annoying than the default.
GRML Zsh should be the default tbh, that always prints the result of the last command.
next prev parent reply other threads:[~2019-09-10 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 16:02 fc-cache -f --> fc-cache -fv in the manual Joshua Branson
2019-09-10 17:00 ` Tobias Geerinckx-Rice
2019-09-10 17:32 ` Danny Milosavljevic
2019-09-10 17:47 ` Tobias Geerinckx-Rice
2019-09-10 22:56 ` P via Development of GNU Guix and the GNU System distribution. [this message]
2019-09-11 14:37 ` Joshua Branson
2019-09-11 15:59 ` Tobias Geerinckx-Rice
2019-09-11 14:39 ` Joshua Branson
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='0Ka_5Nq1eZAuRrWUl5Gq8NioBvoc2FEYyTAnt-C0XAd_QvYSI1TjIxzKFzmX0D_nAMRpGmalPDhUx6RkQLeCNMjyD8EsYawwcChhzK7T-h4=@protonmail.com' \
--to=guix-devel@gnu.org \
--cc=dannym@scratchpost.org \
--cc=jbranso@dismail.de \
--cc=pronaip@protonmail.com \
/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.