From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 34498@debbugs.gnu.org
Subject: bug#34498: Confusing msgid " Running value is ~s.~%"
Date: Fri, 19 Apr 2019 10:06:18 +0200 [thread overview]
Message-ID: <87bm12iflx.fsf@gnu.org> (raw)
In-Reply-To: <20190418172437.zdrwnqlnm5mmidh3@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Thu, 18 Apr 2019 19:24:37 +0200")
Hi Florian,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> On Thu, Apr 18, 2019 at 06:37:34PM +0200, Ludovic Courtès wrote:
>> Can you suggest a better comment?
>>
>
> Maybe: ;; TRANSLATORS: 'running' is the name of a variable.
That’s not quite true though (it’s a slot in the <service> class,
technically.)
I agree that “running value” is a confusing phrase. That’s why I wrote
that it’s a PID most of the time, hoping that this would clarify it.
> I thought #:running describes the manner in which the service is
> running. Maybe I misunderstand.
Yeah, it’s really just a PID:
--8<---------------cut here---------------start------------->8---
$ sudo herd status nscd
Status of nscd:
It is started.
Running value is 446.
It is enabled.
Provides (nscd).
Requires (user-processes).
Conflicts with ().
Will be respawned.
--8<---------------cut here---------------end--------------->8---
We’ve just received new translations, so let’s see if that looks good.
Thanks,
Ludo’.
prev parent reply other threads:[~2019-04-19 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 6:10 bug#34498: Confusing msgid " Running value is ~s.~%" pelzflorian (Florian Pelz)
2019-04-18 10:34 ` Ludovic Courtès
2019-04-18 15:41 ` pelzflorian (Florian Pelz)
2019-04-18 16:37 ` Ludovic Courtès
2019-04-18 17:24 ` pelzflorian (Florian Pelz)
2019-04-19 8:06 ` Ludovic Courtès [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=87bm12iflx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34498@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).