On 2023/01/23 19:09:59 +1100, Mark Jamsek <mark@jamsek.com> wrote:
> > > > > I can't see why the line has been wrapped; chattygot fits on the above
> > > > > line?
> > > > 
> > > > the above line is 79 columns, that was 80 :)
> > > 
> > > Oh whoops, I've been doing it wrong! I always thought it was [1,80] not
> > > [1,80)  :)

honestly I never cared too much about the exact column length, but a
line that's 80+ chars long is shown as if it continues on mg(1) in a
80x24 xterm (the '$' character at EOL) so that's why I fold them.
most of the times i just do it manually as i read the code, just to
see how much stuff there's after (mg doesn't split overflowing lines.)

hope it's not annoying.

maybe i should just use another editor (and sometimes I even do) but
mg is a pleasure to use :)

> > style(9) says "All code should fit in 80 columns."
> > I don't know if that includes code in diffs which has an extra column
> > at the beginning.

nitpick: per style code is indented with tabs (except for places where
it's not) so the extra column added at the beginning doesn't count

> > I usually try to wrap at less than 80 but there are
> > cases where I just let run up to 80. In any case, not a big deal.
> 
> I'm really not sure about the diff part either, but I always interpreted
> that line in style(9) to be 80 columns inclusive because it's 1-based;
> that is, if the last character is on column 80 that's ok. But it sounds
> like it's exclusive.
> 
> Like you say, not a big deal, but I never even considered it was [1,80)
> till I read op's reply so it's good to now know!

yeah, i didn't want to nitpick and don't want to sound annoying nor
religously attached to the 80 columns or style(9).  I just prefer to
being able to read the code/diffs in my 80x24 xterm 8-)