Re: [math-fun] DO sweat it
VE>The radiative heat flow to the droplets goes like their area on the glass, but the heat required to raise their temperature by one degree goes like their volume. The small drops therefore heat up faster than the large drops and their surface tension diminishes faster, causing them to become unstable (against gravity) first. Veit Sorry, no, the larger ones still fall first, as before. I was merely asking why they only fell when warm, and you said the magic words that *surface tension* declines with temperature. So the smaller ones need to get hotter. Perfect. Thanks! --rwg On Apr 25, 2011, at 7:18 PM, Bill Gosper wrote:
Sprinkle some water on the horizontal inside surface of the opened glass door of a room-temperature toaster oven. Close the door, and wait half a minute for the larger drops to run down. Press TOAST. What happens to the remaining drops?
I would have expected them to evaporate. Instead, they run down in decreasing order of size, at least for me, well before reaching the boiling point. Why?? --rwg
How do I stop idiot GMail from linebreaking? IBM punch cards were 80 column.
On Mon, Apr 25, 2011 at 5:28 PM, Bill Gosper <billgosper@gmail.com> wrote:
How do I stop idiot GMail from linebreaking? IBM punch cards were 80 column.
http://groups.google.com/group/google-mail-problem-solving-uk/browse_thread/... This suggests you can't without sending HTML email, which isn't allowed on this list. I have a greasemonkey script that makes the message composition area be a monospace font even in plain text mode; it shouldn't be hard to change it to set the width to 78 characters so you can see where your message will wrap. -- Mike Stay - metaweta@gmail.com http://www.cs.auckland.ac.nz/~mike http://reperiendi.wordpress.com
Unfortunately, I think that this is part of the traditional internet email standard. Apparently, these standards had to cope with Unix/C people who couldn't count past 255, so line lengths are _required_ to be broken up in (apparently) as odd a place as possible. You will also see from time to time a ">" character inserted before the word "from" if it occurs as the first character of a line. This is because "<cr>From" is the _delimiter_ for email! But I'd still rather use ascii character based email; "html"/"rich text" email can hide all kinds of non-sense that you don't want to allow. Then there is always the O(n^2) growth in delimiters from quoting quotes which also quote quotes. You can see this O(n^2) growth in operation at the end of math-fun emails which have a 4-line terminator at every level of quoting! [O(n^2) because people tend to quote the _entire_ email each time they reply.] At 06:00 PM 4/25/2011, Mike Stay wrote:
On Mon, Apr 25, 2011 at 5:28 PM, Bill Gosper <billgosper@gmail.com> wrote:
How do I stop idiot GMail from linebreaking? IBM punch cards were 80 column.
http://groups.google.com/group/google-mail-problem-solving-uk/browse_thread/...
This suggests you can't without sending HTML email, which isn't allowed on this list. I have a greasemonkey script that makes the message composition area be a monospace font even in plain text mode; it shouldn't be hard to change it to set the width to 78 characters so you can see where your message will wrap. -- Mike Stay - metaweta@gmail.com http://www.cs.auckland.ac.nz/~mike http://reperiendi.wordpress.com
It is true, to quote RFC 2282: "Each line of characters must be no more than 998 characters, and should be no more than 78 characters, excluding the CRLF." On Mon, Apr 25, 2011 at 7:11 PM, Henry Baker <hbaker1@pipeline.com> wrote:
Unfortunately, I think that this is part of the traditional internet email standard.
Apparently, these standards had to cope with Unix/C people who couldn't count past 255, so line lengths are _required_ to be broken up in (apparently) as odd a place as possible.
You will also see from time to time a ">" character inserted before the word "from" if it occurs as the first character of a line. This is because "<cr>From" is the _delimiter_ for email!
But I'd still rather use ascii character based email; "html"/"rich text" email can hide all kinds of non-sense that you don't want to allow.
Then there is always the O(n^2) growth in delimiters from quoting quotes which also quote quotes. You can see this O(n^2) growth in operation at the end of math-fun emails which have a 4-line terminator at every level of quoting!
[O(n^2) because people tend to quote the _entire_ email each time they reply.]
At 06:00 PM 4/25/2011, Mike Stay wrote:
On Mon, Apr 25, 2011 at 5:28 PM, Bill Gosper <billgosper@gmail.com> wrote:
How do I stop idiot GMail from linebreaking? IBM punch cards were 80 column.
http://groups.google.com/group/google-mail-problem-solving-uk/browse_thread/...
This suggests you can't without sending HTML email, which isn't allowed on this list. I have a greasemonkey script that makes the message composition area be a monospace font even in plain text mode; it shouldn't be hard to change it to set the width to 78 characters so you can see where your message will wrap. -- Mike Stay - metaweta@gmail.com http://www.cs.auckland.ac.nz/~mike http://reperiendi.wordpress.com
_______________________________________________ math-fun mailing list math-fun@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/math-fun
On 25 Apr 2011 at 20:41, quad wrote:
It is true, to quote RFC 2282:
"Each line of characters must be no more than 998 characters, and should be no more than 78 characters, excluding the CRLF."
On Mon, Apr 25, 2011 at 7:11 PM, Henry Baker <hbaker1@pipeline.com> wrote:
Unfortunately, I think that this is part of the traditional internet email standard.
Apparently, these standards had to cope with Unix/C people who couldn't count past 255, so line lengths are _required_ to be broken up in (apparently) as odd a place as possible.
We must have a different reading of things: First, for a math list I'd think that we could agree that 998 != 255. Second, there's a difference between "required" and "should be". Fact is, long lines work fine [and you can use text-flowed if 1000 chars isn't long enough of a line for you. /Bernie\ -- Bernie Cosell Fantasy Farm Fibers mailto:bernie@fantasyfarm.com Pearisburg, VA --> Too many people, too few sheep <--
On Tue, Apr 26, 2011 at 8:21 AM, Henry Baker <hbaker1@pipeline.com> wrote:
Hmmm... Is there a positive base x and a base y (hopefully rational) such that 998 (base x) = 255 (base y) ?
Certainly! When x=1/3 and y=1, both sides equal 12! --Michael
At 08:04 PM 4/25/2011, Bernie Cosell wrote:
we could agree that 998 != 255.
_______________________________________________ math-fun mailing list math-fun@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/math-fun
-- Forewarned is worth an octopus in the bush.
On 25 Apr 2011 at 18:11, Henry Baker wrote:
Unfortunately, I think that this is part of the traditional internet email .. standard.
Apparently, these standards had to cope with Unix/C people who couldn't count past 255, so line lengths are _required_ to be broken up in (apparently) as odd a place as possible.
this is just wrong. You're mixing up a bunch of things here. The *protocol* [which has nothing whatever to do with the actual formatting of the data in the email message] specifies that lines *cannot* be longer than 998 characters. The protocol is a line-at-a-time protocol and they wanted to make it possible for the servers to be able to read the message into a simple, finite buffer. but there's no constraint [other than the above] on the format of the *content* of an email message and so there's no particular reason why URLs need to be "oddly wrapped" [unless they're truly unbelievably long, and that's what tinyurl is for]. Email also accomodates folk who prefer "paragraph at a time", which is "text-flowed"
You will also see from time to time a ">" character inserted before the word "from" if it occurs as the first character of a line. This is because ..."<cr>From" is the _delimiter_ for email!
that's close: it is an anomaly left over from the particular sendmail formatted the so-called "unix format" mailbox. Email, itself, has not such requirements nor constraints, it is only that _some_ mail servers mung messages by sticking in that stupid ">".
But I'd still rather use ascii character based email; "html"/"rich text" email can hide all kinds of non-sense that you don't want to allow.
Do you mes "ascii" for *ANYTHING* else you do? Do you do your calendar, slides, memoranda, documents, reports, IMs, web pages,.... *ANYTHING* in "ascii"? That's a horrible relic of the 70s. And just for the record; HTML is also "just text". Rich text isn't, agreed, and I actually think that of all of the many many 'fancier email' proposals I've seen over the decades, I think that RTF was probably the best of them [an early IEEE proposed-standard used ePS]
Then there is always the O(n^2) growth in delimiters from quoting quotes which also quote quotes. You can see this O(n^2) growth in operation at the end of math-fun emails which have a 4-line terminator at every level of quoting!
[O(n^2) because people tend to quote the _entire_ email each time they reply.]
We agree: that "original message follows" is one of the worst and stupidest conventions to have come down the pike. the doing of Microsoft, I think -- I think they're email client was the first I saw that did that. Let's test -- my email client allows me to compose long lines. So this: http://groups.google.com/group/google-mail-problem-solving-uk/browse_thread/... shouldn't have gotten wrapped. /Bernie\ -- Bernie Cosell Fantasy Farm Fibers mailto:bernie@fantasyfarm.com Pearisburg, VA --> Too many people, too few sheep <--
Apparently, these standards had to cope with Unix/C people who couldn't count past 255, so line lengths are _required_ to be broken up in (apparently) as odd a place as possible.
this is just wrong. You're mixing up a bunch of things here.
Well it *is* true UNIX/C people can't count past 255. **scurries back under a bridge (made of sexps and parentheses)**
participants (6)
-
Bernie Cosell -
Bill Gosper -
Henry Baker -
Michael Kleber -
Mike Stay -
quad