unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Pierre Neidhardt <ambrevar@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: units_cur
Date: Sat, 31 Mar 2018 10:07:00 +0530	[thread overview]
Message-ID: <87efk0zwr7.fsf@gmail.com> (raw)
In-Reply-To: <87po3lldzs.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 607 bytes --]


Ludovic Courtès <ludo@gnu.org> writes:

> Looking more closely, you might be able to add a ~/.units file with:
>
>   include my-updated-currency.units

Note that the actual command must start with a `!`, so it would be:

   !include my-updated-currency.units

> Could you check if that works?

It does.  This would definitely work, but then what about the failing
`sudo units_cur`?

I think this should be documented.  Either by patching the documentation
of units_cur itself so that if run with `sudo`, it displays the above
hint instead.

What do you think?

--
Pierre Neidhardt

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-03-31  4:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 10:11 units_cur Pierre Neidhardt
2018-03-27 21:01 ` units_cur Ludovic Courtès
2018-03-30 11:15   ` units_cur Pierre Neidhardt
2018-03-30 16:33     ` units_cur Ludovic Courtès
2018-03-31  4:37       ` Pierre Neidhardt [this message]
2018-03-31 16:18         ` units_cur Ludovic Courtès
2018-03-31 16:40           ` units_cur Pierre Neidhardt
2018-03-31 17:10             ` units_cur Ludovic Courtès
2018-04-01  6:16               ` units_cur Pierre Neidhardt
2018-04-01 13:06                 ` units_cur Pierre Neidhardt
2018-04-01 13:37                   ` units_cur Mathieu Lirzin
2018-03-31  4:51       ` units_cur Pierre Neidhardt
2018-03-31  7:01         ` units_cur Pierre Neidhardt
2018-03-31 16:16           ` units_cur 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

  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=87efk0zwr7.fsf@gmail.com \
    --to=ambrevar@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=ludo@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).