that typo

Sorry I had to go on travelling after making that puckish remark, and
have only just got the laptop working with LAN.

Carl's practice of cutting the context out of everything he quotes led
to the original going missing. Which referred to Alaska tunings having
an 1997-cent flat octave.

I've bought a couple of CDs of Silbermann organ music here in Dresden
one of which refers to the small organ in Freiberg with its supposedly
unaltered temperament ... however I can't listen to 'em yet!

~~~T~~~

> I've bought a couple of CDs of Silbermann organ music here in Dresden
> one of which refers to the small organ in Freiberg with its supposedly
> unaltered temperament ... however I can't listen to 'em yet!
>
> ~~~T~~~

Unaltered since...? I would imagine it'd be altered
one way or the other (either by man or by nature).

-Carl

> Carl's practice of cutting the context out of everything
> he quotes led to the original going missing.

The original is quite visible to web users.

The reason I trim context is twofold:

1. If you don't, messages in long threads get unweildy.
It is appropriate to trim items that have been settled.

2. But usually I trim before this point due to e-mail
wrapping problems. I refuse to post quoted text that's
badly wrapped. It's illegible crap and it shouldn't be
posted. I know several people who stopped reading the
list because of it. Blame the e-mail RFC for requiring
hard wraps every 76 chars.
To combat the problem, I reformat more text (by hand)
than anyone I've ever seen post to this list. But I
have limits to what I'll do.
Insert returns manually at around 45 chars to allow
ample room for replies, or set your client to hard wrap
narrow, and watch me trim less of your context.
Bravo to monz for pioneering this. Narrow text is
easier to read, too.

-Carl

Hi Carl,

--- In tuning@yahoogroups.com, "Carl Lumma" <clumma@...> wrote:

> 2. But usually I trim before this point due to e-mail
> wrapping problems. I refuse to post quoted text that's
> badly wrapped. It's illegible crap and it shouldn't be
> posted. I know several people who stopped reading the
> list because of it. Blame the e-mail RFC for requiring
> hard wraps every 76 chars.
> To combat the problem, I reformat more text (by hand)
> than anyone I've ever seen post to this list.

Liar! *I* reformat more text (by hand) than anyone
you've ever seen post to the list.

More on this below ...

> But I have limits to what I'll do.
> Insert returns manually at around 45 chars to allow
> ample room for replies, or set your client to hard wrap
> narrow, and watch me trim less of your context.
> Bravo to monz for pioneering this. Narrow text is
> easier to read, too.

OK, thanks. ;-)

The difference between us is that i don't have limits
to what i'll do. If i intend to reply to something
that requires a quote, i quote as much of it as i have
to and only snip what really isn't absolutely necessary,
and then i spend ridiculous amounts of time manually
inserting line-breaks and reformatting the text so
that it doesn't look like crap.

But i sure do wish everyone else would just type
short lines like i do, so that i (and you) wouldn't
have to do this, and so that posts from all of those
who don't do it wouldn't be filled with so much
illegible crap.

-monz
http://tonalsoft.com
Tonescape microtonal music software