From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH 5/6] rio: update man pages re: control files
Date: Thu, 28 Sep 2023 00:12:15 -0700 [thread overview]
Message-ID: <688E36C2B65C16FC48CE24A8735871D2@smtp.pobox.com> (raw)
In-Reply-To: <AD6BD0841D782A70E4C68E8E9493A8B4@smtp.pobox.com>
The code changes for rio are from last year, AFAICT, and I had some
scripts that had used the old files. It caused more confusion on my
end because I was referring to the documentation and it wasn't updated
along with the code.
Quoth Romano <unobe@cpan.org>:
> ---
> diff 0b5b2d58047b698564f6b1955a31cbcc95570abb 47ddd324c0c118ca5d6662e82b094e94a1cfb771
> --- a/sys/man/1/rio
> +++ b/sys/man/1/rio
> @@ -488,7 +488,6 @@
> it interprets all mouse events, gets all keyboard characters,
> and determines what appears on the screen.
> .SH FILES
> -.TF /srv/riowctl.\fIuser\fP.\fIpid\fP
> .TP
> .B /lib/font/bit/*
> font directories
> @@ -505,11 +504,6 @@
> .B /srv/rio.\fIuser\fP.\fIpid\fP
> Server end of
> .IR rio .
> -.TP
> -.B /srv/riowctl.\fIuser\fP.\fIpid\fP
> -Named pipe for
> -.I wctl
> -messages.
> .SH SOURCE
> .TF /sys/src/cmd/rio
> .TP
> --- a/sys/man/4/rio
> +++ b/sys/man/4/rio
> @@ -39,16 +39,6 @@
> is set to this service name within processes running under the control
> of each invocation of
> .IR rio .
> -Similarly,
> -.I rio
> -posts a named pipe to access the window creation features
> -(see
> -.B window
> -in
> -.IR rio (1))
> -from outside
> -its name space; this is named in
> -.BR $wctl .
> .PP
> A
> .I mount
> @@ -354,8 +344,8 @@
> may create windows,
> .B wctl
> .B new
> -messages may also be written to the named pipe identified by
> -.BR $wctl .
> +messages may also be written as attach arguments when mounting
> +.B /srv/rio.\fIuser\fP.\fIpid\fP .
> .TP
> .B wdir
> is a read/write text file containing
>
>
prev parent reply other threads:[~2023-09-28 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 5:54 Romano
2023-09-28 7:12 ` unobe [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=688E36C2B65C16FC48CE24A8735871D2@smtp.pobox.com \
--to=unobe@cpan.org \
--cc=9front@9front.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 NNTP newsgroup(s).