Good grief. My apologies Stu. Thanks Daniel for showing me another reason to nag about Gmail to google.<br><br>
<div><span class="gmail_quote">On 5/19/06, <b class="gmail_sendername">Daniel Remenak</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On 5/19/06, Tom Booker <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<br>> I hope you dont take this to be directed at you, Stu, but I need to say
<br>> something, and yours was a good example.<br>><br>> PLEASE!! Anyone that is reading this, do not paste your console output! I<br>> cannot read it in my gmail web interface, because I have a tiny monitor (
<br>> 14.1" which is like around 13" viewable), so I have to use 640x480 for my<br>> resolution in order to be able to see anything, and then the adverts for the<br>> web interface cut everything off halfway.
<br>><br>> Again, I ask everyone to please attach console output, do not paste it in<br>> either bugs on bugzilla, nor here.<br>><br><br>No offense intended, but Stu's message DID have two attachments. If<br>
you don't believe me, click on his message, then More Options, then<br>Show Original, and you'll find two text file attachments in encoded in<br>base64. The fact that gmail chooses not to tell you they're<br>attachments and displays them inline stems from the fact that they
<br>have a content-type of text/plain. I don't know of any options to<br>disable that behavior.<br><br>> --------------040006020306030603060203<br>> Content-Type: text/plain;<br>> name="winetest-alsa.out"
<br>> Content-Transfer-Encoding: base64<br>> Content-Disposition: inline;<br>> filename="winetest-alsa.out"<br><br><br></blockquote></div><br>