Re: AWS Coding Styles (and about boring plain-linear text files in the end)

[sjw <simon.j.wright@mac.com>]

On Jan 18, 8:50 am, 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>  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...

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