From: Tero Tilus <tero@tilus.net>
To: Sup users <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] illegible encoding when exiting vim
Date: Sun, 30 Jan 2011 00:46:27 +0200 [thread overview]
Message-ID: <1296340383-sup-5241@tilus.net> (raw)
In-Reply-To: <20110129141920.nfxc8118ysss0840@webmail.plecavalier.com>
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
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-01-29 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 15:20 Philippe LeCavalier
2011-01-29 19:00 ` Tero Tilus
[not found] ` <20110129141920.nfxc8118ysss0840@webmail.plecavalier.com>
2011-01-29 22:46 ` Tero Tilus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1296340383-sup-5241@tilus.net \
--to=tero@tilus.net \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox