From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] proof and page
Date: Sat, 05 Dec 2020 19:33:30 -0500 [thread overview]
Message-ID: <886EE2CD-2783-46A4-8BED-B1E2F79B006F@stanleylieber.com> (raw)
In-Reply-To: <0AA95C236BB3F37543EC1DCFD4360549@eigenstate.org>
On December 5, 2020 7:19:52 PM EST, ori@eigenstate.org wrote:
>Quoth Stuart Morrow <morrow.stuart@gmail.com>:
>> Probably the reason for the semicolon was it's actually a sentence
>> that way. So I followed that line of thought with my '--'.
>>
>> Anyway, I was in proof (quite a few days ago now, sorry for delay)
>> making it consistent with what I did to page (don't know why I didn't
>> think to do that earlier, when the whole point of the page patch was
>> consistency) and now I think we should just delete proof, at least
>> provided nobody claims to use it. The whole thing is bugs. Easy to
>> fix, but still. It doesn't do anything that page doesn't do better.
>>
>> Here's what would need to change:
>>
>> man (delete -p or alias it to -P)
>> man(1)
>> troff(1)
>> rio(1), which inexplicably references proof(1).
>>
>> Executables stick around after the source is gone (I still have
>> ape/mv|cp), so I would want the deletion of cmd/proof to be on a
>> time-delay, so that that one last bug fix ('illegal;') can mk install
>> for everyone.
>>
>> Stuart
>>
>
>I'm ok with this, as long as nobody else objects.
i don't use proof at all.
sl
prev parent reply other threads:[~2020-12-06 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABB-WO_G4O29KAMOB5oq-P7CV_KgQeMMZnjc29tyJv1RwsH3Mw@mail.gmail.com>
2020-11-30 21:10 ` ori
2020-12-03 17:55 ` Stuart Morrow
2020-12-06 0:19 ` ori
2020-12-06 0:33 ` Stanley Lieber [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=886EE2CD-2783-46A4-8BED-B1E2F79B006F@stanleylieber.com \
--to=sl@stanleylieber.com \
--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).