Subject: Re: [sup-talk] illegible encoding when exiting vim

From: Tero Tilus <[email-masked]>
Date: Sun, 30 Jan 2011 00:46:27 +0200

Philippe LeCavalier, 2011-01-29 22:19:
> See attached.

Holy crap!  That's most likely a jpeg image right there.  At the top
you can see a snippet of XMP metadata.  After that there's app data
segment, which apparently contains embedded ICC profile.

How did you do that?!  :-O

You could do some more debugging.  Save the message in vim, check the
filename, but do not exit.  Go check the contents of the file using
another editor or a pager.  What do you see?

If you re-enter vim from reply-mode, does the (supposedly raw jpeg
image) garbage appear in editor?

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Philippe LeCavalier <[email-masked]>
Date: Sat, 29 Jan 2011 09:20:38 -0600

Hi All.

I'm new to Sup. I'm almost switched over from Evo -yes. drastic
change, I know- All but one issues remains. When I exit vim and return
to the compose-mode window, hundreds of lines of illegible encoding is
added to the bottom of the msg. I imagine I'm not the firs to
encounter this. My first guess was the encoding support but adding
ncursesw didn't do anything other than suppress the warning of the
missing gem in the log buffer.

My relevant system info is here[1]. If I forgot anything please ask.
Thanks in advance for any guidance.

[1] http://paste.debian.net/106026/

Cheers,
Phil

---

From: Tero Tilus <[email-masked]>
Date: Sat, 29 Jan 2011 21:00:48 +0200

Philippe LeCavalier, 2011-01-29 17:20:
> When I exit vim and return to the compose-mode window, hundreds of
> lines of illegible encoding is added to the bottom of the msg.

Could you provide a screenshots (minimal mail in vim, compose-mode
after vim) demonstrating the behavior you described.

> If I forgot anything please ask.

$ ruby --version