On Sat, 25 Jul 2015 18:34:30 +0200, Laura Creighton <l...@openend.se> wrote:
> Gmail eats Python. We just saw this mail back from Sebastian Luque > which says in part: >>>> try: all_your_code_which_is_happy_with_non_scalars except >>>> WhateverErrorPythonGivesYouWhenYouTryThisWithScalars: >>>> whatever_you_want_to_do_when_this_happens > Ow! Gmail is understanding the >>> I stuck in as 'this is from the > python console as a quoting marker and thinks it can reflow that. > I think that splunqe must already have gmail set for plain text or > else even worse mangling must show up. > How do you teach gmail not to reflow what it thinks of as 'other > people's quoted text'? Apologies for all the concern the formatting of the quoted message in my reply has generated. I actually cannot see the multiple ">" you quote here on my original follow-up message. I can tell you I'm using Emacs Gnus, and when viewing my un-processed message, that snippet looks like this: >> try: all_your_code_which_is_happy_with_non_scalars except >> WhateverErrorPythonGivesYouWhenYouTryThisWithScalars: >> whatever_you_want_to_do_when_this_happens Sure, the reflowing is probably a feature I've set up to wrap long lines. I know it annoys some people (mildly myself, as I haven't found a fix), but when reading coding fora, I never really take quoted code snippets seriously and always check the original post for these... -- Seb -- https://mail.python.org/mailman/listinfo/python-list
