9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: mkf <9front@9front.org>
Subject: Re: [9front] [FQA] some fixes
Date: Mon, 17 Jan 2022 23:19:48 +0000 (UTC)	[thread overview]
Message-ID: <f745f636-f187-4803-a30e-d3b549edf0ca@sirjofri.de> (raw)
In-Reply-To: <YeXN4N2AJEGQOQWh@bsdforall.org>

Hello

I'm not a native speaker, but I found some missing words.

Take all I write with a grain of salt. In the end sl will do whatever's 
best.

(Comments inline)

sirjofri

17.01.2022 21:13:20 mkf <mkf9@riseup.net>:
> term%  for( i in *.ms) diff -u /n/fqa/$i $i
> --- /n/fqa/appendixl.ms
> +++ appendixl.ms
> @@ -165,7 +165,11 @@
> .html - <br />
> .FG python gif
>
> -Python 2.5.1 is included with the 9front distribution, not because 
> anyone loves Python, but because it was required by Mercurial (also 
> loved by no one), which was required by Google Code (shutting down in 
> 2015). An abject lesson in expediency.
> +Until git9 imported on 9front, python 2.5.1 was included with the 
> 9front distribution, not because anyone loves Python, but because it 
> was required by Mercurial (also loved by no one), which was required by 
> Google Code (shutting down in 2015). An abject lesson in expediency. 
> You still can install it from

"Until git9 [was/has been/some other kind of copula] imported on..."

> +.ihtml a <a 
> href="http://git.9front.org/plan9front/pyhg/HEAD/info.html">
> +http://git.9front.org/plan9front/pyhg/HEAD/info.html
> +.ihtml a
>
> Jeff Sickel ported Python 2.7 to Plan 9.
> .html - Download it <a 
> href="https://bitbucket.org/jas/cpython">here</a>.<p>David du 
> Colombier's notes on to install Python (and Mercurial) are available <a 
> href="http://9legacy.org/9legacy/doc/python/notes">here</a>.
> --- /n/fqa/fqa2.ms
> +++ fqa2.ms
> @@ -408,7 +408,7 @@
> .ihtml a
> join
> .CW
> -#9front
> +#cat-v
> .R
> on
> .CW
> --- /n/fqa/fqa6.ms
> +++ fqa6.ms
> @@ -101,16 +101,25 @@
> pair with attribute file identifies a file to be included in
> the database.  The files are searched in the order they
> appear.  For example:
> -
> +.P1
>       database=
>            file=/lib/ndb/common
>            file=/lib/ndb/local
>            file=/lib/ndb/global
> +.P2

(Thank you for doing this)

> declares the database to be composed of the three files
> -/lib/ndb/common, /lib/ndb/local, and /lib/ndb/global.  By
> -default, /lib/ndb/local is searched before the others.  How-
> -ever, /lib/ndb/local may be included in the database to
> +.CW/lib/ndb/common,
> +.CW /lib/ndb/local,
> +and
> +.CW /lib/ndb/global
> +.  By
> +default,
> +.CW /lib/ndb/local
> + is searched before the others.  How-
> +ever,
> +.CW /lib/ndb/local
> + may be included in the database to
> redefine its ordering.

I'm not sure it this will render nicely, because of whitespace before 
commas and points. I personally prefer \f(CW or the mixed counterpart in 
those cases.

> Within tuples, pairs on the same line bind tighter than
> --- /n/fqa/fqa7.ms
> +++ fqa7.ms
> @@ -1782,6 +1782,8 @@
> .html a <a href="https://www.mail-tester.com">
> .CW https://www.mail-tester.com
> .html a
> +please note that it's currently not possible to get 10 of 10
> +possible scores on 9front, because of lack of DKIM support.

This does sound weird to me. Maybe something like "10 [out] of 10" or 
just "10/10"?

> .html - <a name="7.7.9" />
> .ihtml h2 <h2>
> --- /n/fqa/fqa8.ms
> +++ fqa8.ms
> @@ -2726,11 +2726,11 @@
> .R
> .ihtml h3
>
> -9front ships with
> +9front used to ship with
> .ihtml a <a href="https://www.mercurial-scm.org">
> Mercurial.
> .ihtml a
> -
> +not anymore. it has replaced with git9.

"9front used to ship with Mercurial. Not anymore. It has [been?] 
replaced..."?

> Read:
> .ihtml a <a href="http://fqa.9front.org/fqa5.html#5.2.1.1">
> .I

  reply	other threads:[~2022-01-17 23:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 20:13 mkf
2022-01-17 23:19 ` sirjofri [this message]
2022-01-23 23:07   ` mkf9
2022-01-24  2:53     ` ori
2022-01-25  2:17 ` Stanley Lieber
2022-01-26  6:53   ` mkf9
2022-01-26  8:19     ` cinap_lenrek
2022-01-26  8:34       ` Sigrid Solveig Haflínudóttir
2022-01-26 10:47         ` sirjofri
2022-01-26 14:10           ` hiro
2022-01-26 14:25           ` Stanley Lieber
2022-01-26 10:25       ` Kurt H Maier
2022-01-26 14:23         ` Stanley Lieber
2022-02-03  2:29 ` sl
2022-02-04 10:21   ` mkf9

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=f745f636-f187-4803-a30e-d3b549edf0ca@sirjofri.de \
    --to=sirjofri+ml-9front@sirjofri.de \
    --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).