go ahead... be a heretic | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
G'day Skeeve, I had the same problem, and for the same reason, some years ago. The solution was as ++marto indicated: send with my own email client. I just wanted to add a word of caution when doing this. When I first did this, I formatted the email as (what I thought was) a single <pre> block of monospace text. My email client decided to reformat this into a multi-nested series of <pre> and <p> blocks (I wasn't aware this had happened). When I checked on RT, it said the post was too long to display and indicated an attachment (which showed this horrible, email-client-generated mess). The fix was to change the settings for perlbug@perl.org in my email client to send in "Plain Text Only". All subsequent posts to RT have appeared without any problems. — Ken In reply to Re^3: perlbug - where is my bugreport
by kcott
|
|