[trimming CC list]
Dag-Erling Smorgrav wrote:
Greg Lehey g...@lemis.com writes:
mdoc.samples(7). Now tell me that that's not intuitive.
It would seem mdoc.samples(7) does not teach by example :)
d...@des ~% man -t mdoc.samples | lpr -Plex
Usage: .Rv -std sections 2 and 3
Greg Lehey [EMAIL PROTECTED] writes:
mdoc.samples(7). Now tell me that that's not intuitive.
It would seem mdoc.samples(7) does not teach by example :)
des@des ~% man -t mdoc.samples | lpr -Plex
Usage: .Rv -std sections 2 and 3 only
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To
[trimming CC list]
Dag-Erling Smorgrav wrote:
Greg Lehey [EMAIL PROTECTED] writes:
mdoc.samples(7). Now tell me that that's not intuitive.
It would seem mdoc.samples(7) does not teach by example :)
des@des ~% man -t mdoc.samples | lpr -Plex
Usage: .Rv -std sections 2 and 3 only
Greg Lehey g...@lemis.com writes:
mdoc.samples(7). Now tell me that that's not intuitive.
It would seem mdoc.samples(7) does not teach by example :)
d...@des ~% man -t mdoc.samples | lpr -Plex
Usage: .Rv -std sections 2 and 3 only
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To
[trimming CC list]
Dag-Erling Smorgrav wrote:
Greg Lehey g...@lemis.com writes:
mdoc.samples(7). Now tell me that that's not intuitive.
It would seem mdoc.samples(7) does not teach by example :)
d...@des ~% man -t mdoc.samples | lpr -Plex
Usage: .Rv -std sections 2 and 3 only
This
On Wed, Jun 30, 1999 at 08:02:06PM -0500, Stan Shkolnyy wrote:
On Wed, 30 Jun 1999, Nik Clayton wrote:
Sorry it's taken me a while to reply to this; ironically, most of my time
has been spent on freebsd-doc recently.
On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny wrote:
Sorry it's taken me a while to reply to this; ironically, most of my time
has been spent on freebsd-doc recently.
On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny wrote:
I've come to understanding that lack of documentation is probably one of
the factors that keep the system
On Wed, Jun 30, 1999 at 09:01:03PM +0100, Nik Clayton wrote:
On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny wrote:
I've come to understanding that lack of documentation is probably one of
the factors that keep the system healthy,
I've just spent five minutes trying to
:[...]
:
:I guessed I freaked some people out when I declared that I wanted to
:work on the VM system, discussions in the first few months went with
:half of core talking to me like I didn't know jack when I do know at
:least jack, but had to come up to speed on
On Wed, 30 Jun 1999, Nik Clayton wrote:
Sorry it's taken me a while to reply to this; ironically, most of my time
has been spent on freebsd-doc recently.
On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny wrote:
I've come to understanding that lack of documentation is probably
Sorry it's taken me a while to reply to this; ironically, most of my time
has been spent on freebsd-doc recently.
On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny wrote:
I've come to understanding that lack of documentation is probably one of
the factors that keep the system
On Wed, Jun 30, 1999 at 09:01:03PM +0100, Nik Clayton wrote:
On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny wrote:
I've come to understanding that lack of documentation is probably one of
the factors that keep the system healthy,
I've just spent five minutes trying to
:[...]
:
:I guessed I freaked some people out when I declared that I wanted to
:work on the VM system, discussions in the first few months went with
:half of core talking to me like I didn't know jack when I do know at
:least jack, but had to come up to speed on FreeBSDisms
On Wed, 30 Jun 1999, Nik Clayton wrote:
Sorry it's taken me a while to reply to this; ironically, most of my time
has been spent on freebsd-doc recently.
On Sat, Jun 26, 1999 at 12:03:59PM -0500, Constantine Shkolny wrote:
I've come to understanding that lack of documentation is probably
Greg Lehey wrote:
I've come to understanding that lack of documentation is probably one of
the factors that keep the system healthy, because it keeps the unskilled
people away. I don't know whether it's true but I read in books that
reading code is one of the methods to learn
Greg Lehey wrote:
I've come to understanding that lack of documentation is probably one of
the factors that keep the system healthy, because it keeps the unskilled
people away. I don't know whether it's true but I read in books that
reading code is one of the methods to learn programming.
On Sat, Jun 26, 1999 at 03:08:10PM +0200, Nick Hibma wrote:
And they are going to scream like mad if there isn't any. But in the end
they start reading the code anyway, even if there is docu, because they
don't trust anything but their own eyes and brain.
ports system == really really
On Saturday, June 26, 1999 8:08 AM, Nick Hibma [SMTP:[EMAIL PROTECTED]]
wrote:
Programmers need documentation too.
And they are going to scream like mad if there isn't any. But in the end
they start reading the code anyway, even if there is docu, because they
don't trust anything but their
Hi Chuck,
On Wed, Jun 23, 1999 at 07:20:56PM -0400, Chuck Robey wrote:
But one thing I like is, although FreeBSD *does* try to appease user
demands, it's controlled by programmers, not users, so if something is
a technically extemely evil idea, no matter how the masses yell for it,
it will
On Wed, Jun 23, 1999 at 07:20:56PM -0400, Chuck Robey wrote:
But one thing I like is, although FreeBSD *does* try to appease user
demands, it's controlled by programmers, not users, so if something is
a technically extemely evil idea, no matter how the masses yell for it,
it will NOT
On Sat, Jun 26, 1999 at 03:08:10PM +0200, Nick Hibma wrote:
And they are going to scream like mad if there isn't any. But in the end
they start reading the code anyway, even if there is docu, because they
don't trust anything but their own eyes and brain.
ports system == really really large
On Saturday, June 26, 1999 8:08 AM, Nick Hibma [SMTP:hi...@skylink.it]
wrote:
Programmers need documentation too.
And they are going to scream like mad if there isn't any. But in the end
they start reading the code anyway, even if there is docu, because they
don't trust anything but their
On Saturday, 26 June 1999 at 12:03:59 -0500, Constantine Shkolny wrote:
On Saturday, June 26, 1999 8:08 AM, Nick Hibma [SMTP:hi...@skylink.it]
wrote:
Programmers need documentation too.
And they are going to scream like mad if there isn't any. But in the end
they start reading the code
On Tue, 22 Jun 1999, Jeroen Ruigrok/Asmodai wrote:
I am not fingerpointing here, not am I willing to. I just want to ask all
developers to try and document at least the basic ideas somewhere in a
manpage in order to make it easier for others (like me) who want to get
the documentation on
On Wednesday, 23 June 1999 at 9:12:12 +0300, Taavi Talvik wrote:
On Tue, 22 Jun 1999, Jeroen Ruigrok/Asmodai wrote:
I am not fingerpointing here, not am I willing to. I just want to ask all
developers to try and document at least the basic ideas somewhere in a
manpage in order to make it
In case FreeBSD wants to enter commercial environments, we have to behave
like behaving in commercial environments.
Ok, so let's follow Microsoft's industry-leading documentation standards.
He said "commercial", not "toy".
Given that I've just spent a very unhappy couple of weeks
On Wed, Jun 23, 1999 at 04:39:28PM +0930, Greg Lehey wrote:
But Mark illustrates my point perfectly; developers don't write
documentation. That's what camp followers are for. So far, we have
the ones that whine about the loot and throw mud at us when we march
too slowly, but not enough
On Wed, 23 Jun 1999, Nik Clayton wrote:
[deleted cvs-all from the list of cc's, how'd it get there?
On Wed, Jun 23, 1999 at 04:39:28PM +0930, Greg Lehey wrote:
But Mark illustrates my point perfectly; developers don't write
documentation. That's what camp followers are for. So far, we
On Tue, 22 Jun 1999, Jeroen Ruigrok/Asmodai wrote:
I am not fingerpointing here, not am I willing to. I just want to ask all
developers to try and document at least the basic ideas somewhere in a
manpage in order to make it easier for others (like me) who want to get
the documentation on the
On Wednesday, 23 June 1999 at 9:12:12 +0300, Taavi Talvik wrote:
On Tue, 22 Jun 1999, Jeroen Ruigrok/Asmodai wrote:
I am not fingerpointing here, not am I willing to. I just want to ask all
developers to try and document at least the basic ideas somewhere in a
manpage in order to make it
* Warner Losh (i...@harmony.village.org) [990623 07:43]:
@daemon.ninth-circle.org Jeroen Ruigrok/Asmodai writes:
: No documentation is worse than just a sparse manpage.
ls /usr/share/man/man9 | egrep newbus stuff
Oh, I wasn't implying that the newbus guys didn't document anything. I was
* Warner Losh (i...@harmony.village.org) [990623 07:43]:
daemon.ninth-circle.org Jeroen Ruigrok/Asmodai writes:
: Granted, we can never think of reaching a commercial level on documentating
: the internals/code which all the committers provide.
I think that the documenation that Doug has
In case FreeBSD wants to enter commercial environments, we have to behave
like behaving in commercial environments.
Ok, so let's follow Microsoft's industry-leading documentation standards.
He said commercial, not toy.
Given that I've just spent a very unhappy couple of weeks
On Tuesday, 22 June 1999 at 23:52:25 -0700, Mike Smith wrote:
In case FreeBSD wants to enter commercial environments, we have to behave
like behaving in commercial environments.
Ok, so let's follow Microsoft's industry-leading documentation standards.
He said commercial, not toy.
Given
From the keyboard of Warner Losh:
ls /usr/share/man/man9 | egrep newbus stuff
bus_generic_attach.9.gz
bus_generic_detach.9.gz
[...]
I know. I just don't get an idea of the concept. Or am i missing something
here (something like a meta-manpage or a general description containing
And as to the author: Writing docu while you are implementing something
might work in a commercial environment where you want to be able to
market something before it's sell-by date, but for hobbiests who
basically spend the odd evening doing something, it is too much hassle.
[Cc: line trimmed dramatically]
On Tue, Jun 22, 1999 at 11:52:25PM -0700, Mike Smith wrote:
Given that I've just spent a very unhappy couple of weeks demonstrating
that this toy you're referring to outperforms us by a factor of
anything from 3 to 10 on a range of basic benchmarks, and has
Date: Wed, 23 Jun 1999 09:12:12 +0300 (EEST)
From: Taavi Talvik ta...@uninet.ee
If you write man pages first time, it is quite close to clack magic.
It may seem that way (ref. Arthur C. Clark), but I respectfully
disagree.
It would be really nice if someone comfortant with troff/nroff etc.
On Wed, Jun 23, 1999 at 04:39:28PM +0930, Greg Lehey wrote:
But Mark illustrates my point perfectly; developers don't write
documentation. That's what camp followers are for. So far, we have
the ones that whine about the loot and throw mud at us when we march
too slowly, but not enough
On Wed, 23 Jun 1999, Nik Clayton wrote:
[deleted cvs-all from the list of cc's, how'd it get there?
On Wed, Jun 23, 1999 at 04:39:28PM +0930, Greg Lehey wrote:
But Mark illustrates my point perfectly; developers don't write
documentation. That's what camp followers are for. So far, we
On Wednesday, 23 June 1999 at 9:12:12 +0300, Taavi Talvik wrote:
On Tue, 22 Jun 1999, Jeroen Ruigrok/Asmodai wrote:
If you write man pages first time, it is quite close to clack magic.
It would be really nice if someone comfortant with troff/nroff etc.
would make Handbook page describing
On Wed, 23 Jun 1999, Greg Lehey wrote:
There's a man page for it :-)
mdoc.samples(7). Now tell me that that's not intuitive.
Is it just me or does everyone get a (non-fatal) error as mdoc.samples(7)
is formatted? The perfect man page for an error as well :-)
Andrew
To Unsubscribe:
On Thu, 24 Jun 1999 and...@ugh.net.au wrote:
On Wed, 23 Jun 1999, Greg Lehey wrote:
There's a man page for it :-)
mdoc.samples(7). Now tell me that that's not intuitive.
Is it just me or does everyone get a (non-fatal) error as mdoc.samples(7)
is formatted? The perfect man page
On Wed, 23 Jun 1999, Chuck Robey wrote:
I saw it flash by too quick to read, the first time, but when I tried to
People with no lag
The error is:
Usage: .Rv -std sections 2 and 3 only
Probably because of caching, I can't see any error just running man
Yep...rm
On Thu, 24 Jun 1999 and...@ugh.net.au wrote:
On Wed, 23 Jun 1999, Chuck Robey wrote:
I saw it flash by too quick to read, the first time, but when I tried to
People with no lag
The error is:
Usage: .Rv -std sections 2 and 3 only
That error is funny! It's true, .Rv -std is
* Mark Newton ([EMAIL PROTECTED]) [990622 17:38]:
Hellmuth Michaelis wrote:
And as to the author: Writing docu while you are implementing something
might work in a commercial environment where you want to be able to
market something before it's sell-by date, but for hobbiests who
* Mike Smith ([EMAIL PROTECTED]) [990622 17:38]:
And they might, too. phk has frequently expressed a desire to either
write documentation on existing systems, or at least help others do
so.
No offence meant, but we can see how much of this has actually
materialised.
Hence I started
On Tuesday, 22 June 1999 at 1:42:05 -0700, Mike Smith wrote:
And they might, too. phk has frequently expressed a desire to either
write documentation on existing systems, or at least help others do
so.
No offence meant, but we can see how much of this has actually
materialised.
None
In message [EMAIL PROTECTED] Jeroen Ruigrok/Asmodai
writes:
: Granted, we can never think of reaching a commercial level on documentating
: the internals/code which all the committers provide.
I think that the documenation that Doug has written to date EXCEEDS so
called commercial standards.
On Tuesday, 22 June 1999 at 1:23:24 -0700, Mike Smith wrote:
Anyway, i don't think you are asking for too much - of what use is a shiny
new design of a new subsystem in the very basic FreeBSD architecture if just
some handful few people knew how it works and how to use it ?
Gosh, that would
And they might, too. phk has frequently expressed a desire to either
write documentation on existing systems, or at least help others do
so.
No offence meant, but we can see how much of this has actually
materialised.
It has never happened that way (anywhere, on any project),
Of
In short: Where's the patch?
And as to the author: Writing docu while you are implementing something
might work in a commercial environment where you want to be able to
market something before it's sell-by date, but for hobbiests who
basically spend the odd evening doing something, it is too
Hellmuth Michaelis wrote:
And as to the author: Writing docu while you are implementing something
might work in a commercial environment where you want to be able to
market something before it's sell-by date, but for hobbiests who
basically spend the odd evening doing something, it is
And as to the author: Writing docu while you are implementing something
might work in a commercial environment where you want to be able to
market something before it's sell-by date, but for hobbiests who
basically spend the odd evening doing something, it is too much hassle.
On Tue, 22 Jun 1999, Hellmuth Michaelis wrote:
From the keyboard of Nick Hibma:
And as to the author: Writing docu while you are implementing something
might work in a commercial environment where you want to be able to
market something before it's sell-by date, but for hobbiests who
* Doug Rabson (d...@nlsystems.com) [990622 20:48]:
On Tue, 22 Jun 1999, Hellmuth Michaelis wrote:
From the keyboard of Nick Hibma:
And as to the author: Writing docu while you are implementing something
might work in a commercial environment where you want to be able to
market
* Mark Newton (new...@internode.com.au) [990622 17:38]:
Hellmuth Michaelis wrote:
And as to the author: Writing docu while you are implementing something
might work in a commercial environment where you want to be able to
market something before it's sell-by date, but for hobbiests
* Mike Smith (m...@smith.net.au) [990622 17:38]:
And they might, too. phk has frequently expressed a desire to either
write documentation on existing systems, or at least help others do
so.
No offence meant, but we can see how much of this has actually
materialised.
Hence I started
On Tuesday, 22 June 1999 at 1:42:05 -0700, Mike Smith wrote:
And they might, too. phk has frequently expressed a desire to either
write documentation on existing systems, or at least help others do
so.
No offence meant, but we can see how much of this has actually
materialised.
None
On Tuesday, 22 June 1999 at 19:34:14 +0930, Mark Newton wrote:
Hellmuth Michaelis wrote:
And as to the author: Writing docu while you are implementing something
might work in a commercial environment where you want to be able to
market something before it's sell-by date, but for hobbiests who
On Tuesday, 22 June 1999 at 19:19:47 +0100, Doug Rabson wrote:
On Tue, 22 Jun 1999, Hellmuth Michaelis wrote:
From the keyboard of Nick Hibma:
And as to the author: Writing docu while you are implementing something
might work in a commercial environment where you want to be able to
market
In message 19990622214842.d15...@daemon.ninth-circle.org Jeroen
Ruigrok/Asmodai writes:
: Granted, we can never think of reaching a commercial level on documentating
: the internals/code which all the committers provide.
I think that the documenation that Doug has written to date EXCEEDS so
In message 19990622214019.b15...@daemon.ninth-circle.org Jeroen
Ruigrok/Asmodai writes:
: No documentation is worse than just a sparse manpage.
ls /usr/share/man/man9 | egrep newbus stuff
bus_generic_attach.9.gz
bus_generic_detach.9.gz
bus_generic_map_intr.9.gz
bus_generic_print_child.9.gz
65 matches
Mail list logo
