From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: units_cur
Date: Sat, 31 Mar 2018 18:18:29 +0200 [thread overview]
Message-ID: <87lge8jk16.fsf@gnu.org> (raw)
In-Reply-To: <87efk0zwr7.fsf@gmail.com> (Pierre Neidhardt's message of "Sat, 31 Mar 2018 10:07:00 +0530")
Pierre Neidhardt <ambrevar@gmail.com> skribis:
> 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
OK.
>> 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.
Hmm, dunno. Perhaps we could modify ‘units’ to look for
/var/run/units/currency.units first, and fall back to
/gnu/store/…-units/share/units/currency.units.
We would also arrange for ‘units_cur’ to update the file in /var/run by
default.
WDYT?
I’m not offering to work on the patch, though. :-)
Ludo’.
next prev parent reply other threads:[~2018-03-31 16:18 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 ` units_cur Pierre Neidhardt
2018-03-31 16:18 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lge8jk16.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ambrevar@gmail.com \
--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.
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.