From: renehl@post1.tele.dk (Rene H. Larsen)
Subject: Re: [OT] Line wrapping
Date: 28 Aug 1999 12:51:22 +0200 [thread overview]
Message-ID: <87yaew9o0l.fsf@renehl.ournet.dk> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "28 Aug 1999 00:02:58 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Lee Willis <lee@gbdirect.co.uk> writes:
>
> > I was under the impression that is was common convention (Maybe even
> > RFC?) that you wrap lines at around 72 characters. Anyone any pointers
> > to where this is stated/implied/whatevered ...
>
> I can't recall any RFC stating such (except for headers), but it's,
> uhm, a common convention. :-)
RFC 1855 ("Netiquette Guidelines") specifies that you should
- Limit line length to fewer than 65 characters and end a line
with a carriage return.
but the 72 character limit seems to be a more common convention.
--
#!/usr/bin/perl -w
for$a(0..12){$b[$a]="|"." "x78}for$a(0..78){substr($b[-(sin($a*3.1415/
22)-1)*6.499],$a,1)="*"}$b[6]=~s/ /-/g;print join("\n",@b),"\n";
prev parent reply other threads:[~1999-08-28 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-27 9:56 Lee Willis
1999-08-27 22:02 ` Lars Magne Ingebrigtsen
1999-08-28 10:51 ` Rene H. Larsen [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=87yaew9o0l.fsf@renehl.ournet.dk \
--to=renehl@post1.tele.dk \
/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).