From: Efraim Flashner <efraim@flashner.co.il>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: How to use "setuid-program"?
Date: Sun, 19 Sep 2021 14:37:51 +0300 [thread overview]
Message-ID: <YUchD3ytEsdYqHKZ@3900XT> (raw)
In-Reply-To: <878rzv16lv.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On Fri, Sep 17, 2021 at 06:47:36PM +0200, Tobias Geerinckx-Rice wrote:
> Matthew Brooks 写道：
> > Thanks! I didn't realize there were two versions of the manual, and had
> > been checking the stable one.
>
> This state is extremely confusing and should be improved. How did you
> search/browse to the ‘stable’ manual?
>
> More generally: why did you end up loading a browser to look for the manual
> on the Web, instead of consulting the one on your Guix machine? Were you
> aware of it? Would you have seen a warning at the top of the page, or did
> you click straight through to a section/chapter? Consider this low-budget
> telemetry to find out how better to point users to other options ;-)
>
> Kind regards,
>
> T G-R
I normally check it on the website. I've been toying with writing an
nginx service to serve the html version locally.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-19 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 18:24 How to use "setuid-program"? Matthew Brooks
2021-09-03 18:49 ` Tobias Geerinckx-Rice
2021-09-03 20:16 ` Julien Lepiller
2021-09-17 16:28 ` Matthew Brooks
2021-09-17 16:47 ` Tobias Geerinckx-Rice
2021-09-17 18:26 ` Pascal Lorenz
2021-09-19 11:37 ` Efraim Flashner [this message]
2021-09-19 15:45 ` Leo Famulari
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=YUchD3ytEsdYqHKZ@3900XT \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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).