> Date: Tue, 01 Jan 2019 16:01:36 -0800
> From: Paul Rogers via blfs-support <[email protected]>
>
> > > > (Please wrap your lines to max ~80 chars per b/lfs mailing-lists
> > > > requested netiquette.)
> > > >
> > >
> > > My server's email client doesn't have that option any longer.
> > >
> >
> >
> > So you'll just still send anyhow ...  .
>
> Well, yes, even this brain-damaged email client wraps long lines.


As usual, you miss the by-far central point: (soft-)wrapping is not
the point; it's the knock-on adverse effect on legibility of subsequent
thread replies.


>
> > To smooth your transition, this guide will show you how to retain some
> > popular Classic behaviours, and highlight some new features you may
> > find useful.
>
> I read their guide when they forced me to change.  I was NOT impressed.
> Deleting a message permanently, not just moving it to a Trash folder,
> became "%"!  WHAT!!!!  On what rationale?  Didn't see Ctl-M.
>
> > This is preserved as a keyboard shortcut. Use Ctrl-M on a plain text
> > email to automatically format the text. You can also select a few
> > lines and format just those lines.
> >
> > ====
> >
> > ; use it.
>
> [...] I don't like long lines either. [...]


Where there's a will ... : it took less than 5 minutes to check your
message headers, cross-check w/ your sig, do _one_ simple web-search
('fastmail line-wrap', without the quotes), get the urls quoted earlier,
read what's what, and double-check it all.


If you had had proper regard for the requested b/lfs mailing lists
attitude, then you wouldn't have been still disregarding them and posting
anyhow: you would instead have found the solution way back in mid-2017 .



akh





--
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to