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 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-7-bit
Path: 
 g2news2.google.com!news4.google.com!feeder3.cambriumusenet.nl!feed.tweaknews.nl!195.71.90.67.MISMATCH!news.unit0.net!noris.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Tue, 18 Jan 2011 09:50:23 +0100
From: Georg Bauhaus <rm-host.bauhaus@maps.futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.13) Gecko/20101129 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: AWS Coding Styles (and about boring plain-linear text files in
 the end)
References: <op.vpfsjkfdule2fv@garhos> <C959F8E2.4600%news@findlayw.plus.com>
 <a4cd6433-57ed-49ae-9d30-4f358c28caac@m20g2000prc.googlegroups.com>
In-Reply-To: 
 <a4cd6433-57ed-49ae-9d30-4f358c28caac@m20g2000prc.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <4d355450$0$6891$9b4e6d93@newsspool2.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 18 Jan 2011 09:50:25 CET
NNTP-Posting-Host: 94f05072.newsspool2.arcor-online.net
X-Trace: 
 DXC=MhaA1;_U=PLX36K@\WTHGJA9EHlD;3YcB4Fo<]lROoRA8kF<OcfhCOK?ehMhE]dHMMPCY\c7>ejVHma`IGX2^ePNUJIQ0JnjE^K
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:17485
Date: 2011-01-18T09:50:25+01:00
List-Id: <comp.lang.ada>

On 1/18/11 1:45 AM, Adam Beneschan wrote:
> On Jan 17, 5:47 am, Bill Findlay<n...@findlayw.plus.com>  wrote:
>
>>>> A line should never be longer than 79 characters,
>>>> not counting the line separator.
>>
>>>      I fully agree with this is some sense (just that I use 78
>>>      characters instead of 79).
>>
>> Why 78/79 and not 80, as I have always used?
>
> I tend to make all my windows 80 characters wide.  I 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  to be off by  1, then ;-)  To edit a card  image (an
instructive    idea!)   I'd   toggle-truncate-lines    and   then
set-variable  hscroll-margin to  1 (or  0).   Unfortunately, this
hides the  80th character behind  the truncation indicator  $.  I
cannot believe  that an editor  capable of patching  binary files
and viper-mode forces display  of a useless EOL character?  OTOH,
it is written in C...