From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,429176cb92b1b825
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news2.google.com!postnews.google.com!i32g2000pri.googlegroups.com!not-for-mail
From: sjw <simon.j.wright@mac.com>
Newsgroups: comp.lang.ada
Subject: Re: AWS Coding Styles (and about boring plain-linear text files in
 the end)
Date: Tue, 18 Jan 2011 06:20:03 -0800 (PST)
Organization: http://groups.google.com
Message-ID: 
 <ff3a9046-3b76-4002-8ad9-de8c0f4ee6c7@i32g2000pri.googlegroups.com>
References: <op.vpfsjkfdule2fv@garhos> <C959F8E2.4600%news@findlayw.plus.com>
 <a4cd6433-57ed-49ae-9d30-4f358c28caac@m20g2000prc.googlegroups.com>
 <4d355450$0$6891$9b4e6d93@newsspool2.arcor-online.net>
NNTP-Posting-Host: 20.133.0.13
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1295360403 25640 127.0.0.1 (18 Jan 2011 14:20:03
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 18 Jan 2011 14:20:03 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: i32g2000pri.googlegroups.com; posting-host=20.133.0.13;
 posting-account=_RXWmAoAAADQS3ojtLFDmTNJCT0N2R4U
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.13)
 Gecko/20101203 Firefox/3.6.13,gzip(gfe)
Xref: g2news2.google.com comp.lang.ada:17491
Date: 2011-01-18T06:20:03-08:00
List-Id: <comp.lang.ada>

On Jan 18, 8:50=A0am, Georg Bauhaus <rm-host.bauh...@maps.futureapps.de>
wrote:
> On 1/18/11 1:45 AM, Adam Beneschan wrote:
>
>
>
> > On Jan 17, 5:47 am, Bill Findlay<n...@findlayw.plus.com> =A0wrote:
>
> >>>> A line should never be longer than 79 characters,
> >>>> not counting the line separator.
>
> >>> =A0 =A0 =A0I fully agree with this is some sense (just that I use 78
> >>> =A0 =A0 =A0characters instead of 79).
>
> >> Why 78/79 and not 80, as I have always used?
>
> > I tend to make all my windows 80 characters wide. =A0I use EMACS, which
> > reserves the 80th character for a wrapping indicator, so that if you
> > used it on a source with an 80-character line, EMACS would display
> > only 79 of those on the first line, put a mark in the 80th character
> > indicating that the line is wrapped, and then display the 80th
> > character on the next line.
>
> Emacs seems =A0to be off by =A01, then ;-) =A0To edit a card =A0image (an
> instructive =A0 =A0idea!) =A0 I'd =A0 toggle-truncate-lines =A0 =A0and =
=A0 then
> set-variable =A0hscroll-margin to =A01 (or =A00). =A0 Unfortunately, this
> hides the =A080th character behind =A0the truncation indicator =A0$. =A0I
> cannot believe =A0that an editor =A0capable of patching =A0binary files
> and viper-mode forces display =A0of a useless EOL character? =A0OTOH,
> it is written in C...

Might make sense, alternatively, to make the window 81 columns wide ..