On Mon, 21 Aug 2006, 18:50+0200, Max Laier wrote:
> On Monday 21 August 2006 18:26, Kostik Belousov wrote:
> > is there style(9)-like guide for writing FreeBSD man pages ?
>
> "man mdoc" aka GROFF_MDOC(7) is the closest one I can think of.
+ /usr/share/examples/mdoc/
--
Maxim Konovalov
On Monday 21 August 2006 18:26, Kostik Belousov wrote:
> is there style(9)-like guide for writing FreeBSD man pages ?
"man mdoc" aka GROFF_MDOC(7) is the closest one I can think of.
--
/"\ Best regards, | [EMAIL PROTECTED]
\ / Max Laier | ICQ #6777
>
> On 2005-03-18 00:50, Roman Kurakin <[EMAIL PROTECTED]> wrote:
> >Giorgos Keramidas:
> >>On 2005-03-17 19:33, Roman Kurakin <[EMAIL PROTECTED]> wrote:
> >>>I was unable to refrain from posting this :-)
> >>>
> >>>int i;main(){for(;i["] >>>o, world!\n",'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/
Miguel Mendez:
On Fri, 18 Mar 2005 12:06:12 +1030
Greg 'groggy' Lehey <[EMAIL PROTECTED]> wrote:
On Thursday, 17 March 2005 at 19:33:50 +0300, Roman Kurakin wrote:
Hi,
I was unable to refrain from posting this :-)
int i;main(){for(;i["]
o, world!\n",'/'/'/'));}read(j,i,p){write(j/p+p,i---j,
On Fri, 18 Mar 2005 12:06:12 +1030
Greg 'groggy' Lehey <[EMAIL PROTECTED]> wrote:
> On Thursday, 17 March 2005 at 19:33:50 +0300, Roman Kurakin wrote:
> > Hi,
> >
> > I was unable to refrain from posting this :-)
> >
> > int i;main(){for(;i["] > o, world!\n",'/'/'/'));}read(j,i,p){write(j/p+p,i---
On Thursday, 17 March 2005 at 19:33:50 +0300, Roman Kurakin wrote:
> Hi,
>
> I was unable to refrain from posting this :-)
>
> int i;main(){for(;i["] o, world!\n",'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);}
There used to be a whole culture of this sort of thing. My favourite
one is an anagram
On 2005-03-18 00:50, Roman Kurakin <[EMAIL PROTECTED]> wrote:
>Giorgos Keramidas:
>>On 2005-03-17 19:33, Roman Kurakin <[EMAIL PROTECTED]> wrote:
>>>I was unable to refrain from posting this :-)
>>>
>>>int i;main(){for(;i["]>>o, world!\n",'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);}
>>
>>I've wr
Giorgos Keramidas:
On 2005-03-17 19:33, Roman Kurakin <[EMAIL PROTECTED]> wrote:
Hi,
I was unable to refrain from posting this :-)
int i;main(){for(;i["]
o, world!\n",'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);}
I've written stuff that's probably a bit harder to read, but in Perl :P
% ca
On 2005-03-17 19:33, Roman Kurakin <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I was unable to refrain from posting this :-)
>
> int i;main(){for(;i["] o, world!\n",'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);}
I've written stuff that's probably a bit harder to read, but in Perl :P
% cat filter.pl
#/u
On Sat, Mar 06, 2004 at 12:18:21PM -0800, Tim Kientzle wrote:
> One of the recommendations in style(9) is
> inherently non-portable. I'm trying
> to ensure that the new code I'm writing
> for FreeBSD is portable to other systems,
> so I've been scratching my head over
> how to deal with the versio
At 12:18 PM -0800 3/6/04, Tim Kientzle wrote:
... I've been scratching my head over how to
deal with the version ID code that is supposed
to apear as the first two lines of any FreeBSD
source file:
#include
__FBSDID("$FreeBSD$");
Clearly, I cannot reasonably assume that all
platforms define a __FB
At 20:18 06/03/2004, Tim Kientzle wrote:
I've been scratching my head over
how to deal with the version ID code
that is supposed to apear as the first
two lines of any FreeBSD source file:
#include
__FBSDID("$FreeBSD$");
Clearly, I cannot reasonably assume that all
platforms define a __FBSDID macr
Wes Peters writes:
> Or simply get a wider editor. Seriously. Writing code in 80 columns is
> an anachronism.
No it's not. It's a widely-accepted fact that humans have
difficulty reading lines with more than about 70 characters in
them -- this difficulty increases with age (and is probably al
In message <[EMAIL PROTECTED]> Wes Peters writes:
: Warner Losh wrote:
: >
: > In message <[EMAIL PROTECTED]> Jeroen Ruigrok/Asmodai
:writes:
: > : Often the 80 column boundary reminds me not to use
: > : functions_which_have_crazy_long_names_with_underscores(), but be a
: > : little more brief,
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Jeroen Ruigrok/Asmodai
>writes:
> : Often the 80 column boundary reminds me not to use
> : functions_which_have_crazy_long_names_with_underscores(), but be a
> : little more brief, but not too. ;)
>
> IKnowPeopleThatLikeToHaveParagraphFuncti
Chris Costello wrote:
>
> On Friday, June 30, 2000, Neil Blakey-Milner wrote:
> > No. Anyway, you can set your tab size to whatever you want. So long as
> > it is a _tab_, and not 2 or 4 or 8 spaces. If you're heading into the
> > margin constantly, you should simplify your code, or break it u
In message <[EMAIL PROTECTED]> Jeroen Ruigrok/Asmodai
writes:
: Often the 80 column boundary reminds me not to use
: functions_which_have_crazy_long_names_with_underscores(), but be a
: little more brief, but not too. ;)
IKnowPeopleThatLikeToHaveParagraphFunctionNamesToo();
DrivesMeNutsBecauseTh
-On [2701 09:25], Wes Peters ([EMAIL PROTECTED]) wrote:
>
>Or simply get a wider editor. Seriously. Writing code in 80 columns is
>an anachronism.
Tastes do differ for that.
Often the 80 column boundary reminds me not to use
functions_which_have_crazy_long_names_with_underscores(), but be
-On [2630 19:34], Warner Losh ([EMAIL PROTECTED]) wrote:
>
>I personally like 4 myself, but let's not get into a stupid tab width
>war were people argue about values from 2 to 6 that ends in the
>resolution that 8 might not be right, but reformatting everything
>would suck too bad to change it
Neil Blakey-Milner wrote:
>
> On Fri 2000-06-30 (11:38), Martin Horcicka wrote:
>
> > b. Aren't 8 characters too many?
>
> No. Anyway, you can set your tab size to whatever you want. So long as
> it is a _tab_, and not 2 or 4 or 8 spaces. If you're heading into the
> margin constantly, you s
On Friday, June 30, 2000, Neil Blakey-Milner wrote:
> No. Anyway, you can set your tab size to whatever you want. So long as
> it is a _tab_, and not 2 or 4 or 8 spaces. If you're heading into the
> margin constantly, you should simplify your code, or break it up into
> (preferably reusable) fu
On Fri, 30 Jun 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Warner Losh writes:
> : Don't get us going. No, it isn't. If you run out of room, GW says
>
> Actually that should be CW not GW. CW == Conventional Wisdom.
I was going to point that out, but I didn't want to be
In message <[EMAIL PROTECTED]> Warner Losh writes:
: Don't get us going. No, it isn't. If you run out of room, GW says
Actually that should be CW not GW. CW == Conventional Wisdom.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the me
In message <[EMAIL PROTECTED]> Anders Franzen writes:
: IMHO, I would guess that it can prevent userland from typedefing own types.
: I.e. If a program
: makes an own type : typedef int fd:
:
: and then includes a header file saying : void function(int fd):
: the compiler would complain about t
In message <[EMAIL PROTECTED]> Martin
Horcicka writes:
: 1. Citation:
:
: The kernel has a name associated with parameter types, e.g., in the kernel
: use:
:
: voidfunction(int fd);
:
: In header files visible to user land applications, prototypes that are
: visible must use ei
Martin Horcicka wrote:
> Hi,
>
> I'm just reading the style(9) man page and I don't understand to two
> rules:
>
> 1. Citation:
>
> The kernel has a name associated with parameter types, e.g., in the kernel
> use:
>
> voidfunction(int fd);
>
> In header files visible to user land
On Fri 2000-06-30 (11:38), Martin Horcicka wrote:
> 2. Citation:
>
> Indentation is an 8 character tab. Second level indents are four spaces.
>
> while (cnt < 20)
> z = a + really + long + statement + that + needs +
> two lines + gets + indented + four + spaces +
27 matches
Mail list logo
