-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Austin wrote: > On Fri, 2007-06-15 at 01:13 -0700, David Boles wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> Tim wrote: >> >>> David Boles: >>> >>> >>>> Sniff... Sniff... I think that I smell a troll.... >>>> >>> David, can you do me a favour, and reply to this but leave a >>> blank space between the quoted text and your reply? I'm seeing >>> this strange issue where all the message text is not rendered, >>> it looks like a blank message (just one blank line, not a blank >>> space with invisible text), until there's a blank space in your >>> message, then the rest is displayed. Most of them have just the >>> signature separator and the PGP warning showing. >>> >>> At first I thought they were accidental postings, until I >>> looked at the message source (the whole thing's there, without >>> any obvious faults). And the whole thing is there if I press >>> reply. Yours are the only ones I've seen doing this. >>> >> Hmm.. That's odd. I always leave two blank lines both before and >> after for an 'inline message reply' and two lines after and >> 'end of post' reply. I have been scolded for doing that (it >> should only be one line according to some) but never for what >> you describe. >> >> Does anyone else here see this problem? Is it me or Tim? If it is >> me I will surely try to fix it ASAP. >> >> > > Yep - I am seeing the same thing F7 Evolution 2.10.1 > > John This email <quoted above by you> that you say has the same problem has two blank lines after what I quoted before I replied. Odd. This reply has *three* blank lines after your message. Is it different? - -- David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGclEYrItTyWRhT1YRAkcuAJ9msJtRJGeHAj/LiFePjFzaGVomKgCghLDc aR6nG1Bh8GG/ZluizYfyyPE= =KAJr -----END PGP SIGNATURE-----
