qrux.qed at gmail.com
Fri May 18 12:43:17 PDT 2012
On May 18, 2012, at 9:01 AM, Andrew Benton wrote:
> Qrux <qrux.qed at gmail.com> wrote:
>> BTW, which mail client(s) are folks using that don't wrap
> It doesn't matter what mail readers other people are using...
I disagree. I believe the subject of "which mailer" is indeed
pertinent. I'm guessing (feel free to correct me, but that's the
reason I asked the question in the first place) that the folks who
have clients that don't wrap might be using a textual client (e.g.,
pine, elm, mailx, w/e). If that's the issue, could this issue be
solved by perhaps adding a client that *can* line-wrap into BLFS?
If tools can alleviate restrictions, I think it's better to update
tools. The line-wrapping issue comes from a time when clients
faced line-wrap issues, and the common denominator seemed to be
that the clients at that time *could* line-wrap. So, it probably
made more sense to implement netiquette policies that reflect the
commonalities in that era.
Today, with GUI clients and web-based clients, line-wrapping while
composing is no longer nearly as common--if even an option. So,
the stronger assumption today might be that clients cannot
line-wrap while composing. I'm asking the question about clients
because if the client is indeed a textual one, it's likely to be
FOSS, and as such, could be changed/configured to wrap lines on
the way in. If I had the source to Apple's mail client, I'd take
a crack at auto-line-wrap-on-compose. I don't, so I'm trying to
get at whether we can add tools.
More information about the lfs-dev