think that's because
I have nonstandard sections after .Sh DESCRIPTION. Those could be
subsections but mdoc(7) allows for nonstandard sections when it aids
legibility, which I think it does here.
.\"
.\" Copyright (c) 2022 Evan Silberman
.\" Permission to use, copy, modify, and dis
Oh I guess my first mail made it through after all, dunno what my
confusion was.
Dave Voutila wrote:
>
> Evan Silberman writes:
>
> > OpenBSD is distributed with an authoritative name server daemon, nsd(8),
> > but that distribution doesn't document the format of zon
,
Evan Silberman
.\"
.\" Copyright (c) 2022 Evan Silberman
.\" Permission to use, copy, modify, and distribute this software for any
.\" purpose with or without fee is hereby granted, provided that the above
.\" copyright notice and this permission notice appear in all cop
> On Sep 2, 2021, at 4:05 PM, li...@wrant.com wrote:
>
> Do all manual pages need to be free form texts to suit non-technical
> audiences?
Yes? Who do you think the documentation is for?
Speaking of the first sentence of rm(1):
Remove extraneous word from command description
"non-directory files" reads more naturally and means the same thing as
"non-directory type files".
diff --git a/bin/rm/rm.1 b/bin/rm/rm.1
index a2526a36392..1be2bf31913 100644
--- a/bin/rm/rm.1
+++
> On Jun 15, 2021, at 11:08 AM, dz...@disroot.org wrote:
>
> A presentation is going to have a bigger effect on people than docs.
> That's the point of it.
You must lead an interesting life full of surprises.
Not to provoke a deep philosophical debate about the difference between
Ql, Cm, and Sy, but surely Em isn't the best choice here. A couple other
nits that bothered me in the same general region, I guess your taste
might vary.
Evan Silberman
---
commit
at all, because (as you noted) it's the wrong
implementation in the wrong place and "improving" it by adding more
combination rules here would be a mistake.
--Evan Silberman
The more(1) manual implies that more will accept and handle all the
options less(1) takes, but this is not the case.
--- usr.bin/less/more.1
+++ usr.bin/less/more.1
@@ -65,17 +65,6 @@ It then waits for input from the user.
Scrolling forward switches to the next file,
or exits if there is none.
"Theo de Raadt" wrote:
> And let me comment in general. When diffs contain multiple aspects
> like this, the people can commit sometimes raise their nose at a piece
> and ignore the whole thing. That chunk raises my nose, and I forget
> what else is in your diff.
Good advice. When I get a
bump
Evan Silberman wrote:
> - less(1) should explain what it does before it talks about more(1)
> - reference the COMMANDS section directly when mentioning commands
> - add HISTORY to less.1
> - credit Garret D'Amore in AUTHORS since he is also attributed in the
> source code
be invoked with the options of less(1)
Regards,
Evan Silberman
P.S. patch generated with got(1), neat.
diff 3474c532363343e2e65328f8389848966744ce51
99ab9c189b3b40d7b96cd17ef241b444a0bf456a
blob - 8e6971c243372003b031bba7e37bc50ff3ab8030
blob + 44d9b5001fa119c53e0cf27f9e103d23f5e48dc2
--- usr.bin
"T.J. Townsend" wrote:
> > + You may individually select distribution sets to install
> > + by entering their names or wildcards (e.g. `*.tgz' or
> > + `base*|comp*'), or you may enter `all' to select all the
> > + sets (which is what most users will want
"Theo de Raadt" wrote:
> Evan Silberman wrote:
>
> > - You may now be given the opportunity to configure the time zone
> > - your system will be using (this depends on the installation
> > - media you are using).
> > -
> > - If th
& tech@,
Below is my patch to the installation guide macros from a few weeks ago,
including only hunks jmc had no issues with, and without addressing the
UN*X/UNIX/Unix issue.
thanks!
Evan Silberman
Index: m4.common
===
RCS fil
ecision about sets once and not have to think about it every six months
(every few days if following snaps!). I don't know whether this design
would require the installer to leave additional state behind that it
doesn't already, e.g. a list in /var/db/sets.
Evan Silberman
likely to be a legally
consequential maneuver. (But I am not a lawyer etc etc)
Evan Silberman
Jason McIntyre wrote:
> On Tue, Jul 09, 2019 at 07:43:50AM +0200, Otto Moerbeek wrote:
> > On Mon, Jul 08, 2019 at 10:26:57AM -0700, Evan Silberman wrote:
> >
> > I don't know our stance on Unix vs Un*x. I'll leave this to some
> > native speaker, like jmc@ who knows
request cor fomments
Index: uuid.3
===
RCS file: /cvs/src/lib/libc/uuid/uuid.3,v
retrieving revision 1.6
diff -u -p -r1.6 uuid.3
--- uuid.3 2 Oct 2018 10:55:39 - 1.6
+++ uuid.3 8 Jul 2019 21:15:27 -
@@ -207,4
Otto Moerbeek wrote:
> On Sun, Jul 07, 2019 at 10:44:42PM -0700, Evan Silberman wrote:
>
> > I noticed one thing that bothered me and decided to look for other
> > things that bothered me. Changes were made without reference to the code
> > of the installation prog
happy to provide explanations of any given line edit
on request, but I hope they are self-explanatory. `make allarchs` ran
without issues and I don't seem to have broken any formatting.
Regards,
Evan Silberman
Index: m4.common
===
RCS
21 matches
Mail list logo
