On Mon, Oct 03, 2011 at 04:02:16PM -0400, Mouse wrote:
> One of my correspondents at work has exactly this problem when I send
> nicely formatted text.
>
> > This is, admittedly, less evil than the Android mail client's
> > unalterable behavior of base64-encoding *all* message data, even that
> >
On Mon, Oct 03, 2011 at 02:36:37PM -0400, Thor Lancelot Simon wrote:
> On Mon, Oct 03, 2011 at 11:31:17AM -0700, Erik Fair wrote:
> >
> > On Oct 3, 2011, at 00:56 , Mouse wrote:
> >
> > > [Do you really mean to use paragraph-length lines? I'd suggest against
> > > it; they impair readability
On Mon, Oct 03, 2011 at 12:40:46AM -0700, Erik Fair wrote:
We ought to try and come up with a notification abstraction model
that works reasonably well for each use case, and preferably one
which permits automated userland software response to various
common events.
Trying to enumerate
Hi,
On Mon, Oct 3, 2011 at 2:31 PM, Erik Fair f...@netbsd.org wrote:
On Oct 3, 2011, at 00:56 , Mouse wrote:
[Do you really mean to use paragraph-length lines? I'd suggest against
it; they impair readability significantly, at least for me. Manually
rewrapped in the quotes below.]
On Mon, 3 Oct 2011 00:40:46 -0700
Erik Fair f...@netbsd.org wrote:
Why not a classification/taxonomy of kernel missives? This doesn't mean we
can't continue to have relatively free form (and possibly amusing) text for
those conditions we're not yet prepared to classify/codify yet ('cause
On Mon, 3 Oct 2011 11:31:17 -0700
Erik Fair f...@netbsd.org wrote:
less(1) (or more(1)) doesn't take care of you? The nice thing about such
formatting is that the text can be wrapped at relatively arbitrary word
boundaries, making it more readably displayable on a wider range of display
Ah, Matt, now you've stepped in it: UNIX kernel notifications, and a model for
that. A topic that I glossed over in my previous note.
There are three basic modes of UNIX use:
1. traditional multi-user timesharing system. We in NetBSD land still use our
systems this way sometimes; cf.
[Do you really mean to use paragraph-length lines? I'd suggest
against it; they impair readability significantly, at least for me.
Manually rewrapped in the quotes below.]
less(1) (or more(1)) doesn't take care of you?
Maybe; see below.
The nice thing about such formatting is that the text
[Do you really mean to use paragraph-length lines? [...]]
less(1) (or more(1)) doesn't take care of you?
[...]
I assume you're using Mail.app as a user-agent. Apple used to do
this right -- they wrapped the lines at 72 columns or thereabouts,
but then marked the text as format=flowed in
