From: Philippe LeCavalier <support@plecavalier.com>
To: sup-talk@rubyforge.org
Subject: [sup-talk] illegible encoding when exiting vim
Date: Sat, 29 Jan 2011 09:20:38 -0600 [thread overview]
Message-ID: <20110129092038.6798sdxsmc04oko8@webmail.plecavalier.com> (raw)
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
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2011-01-29 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 15:20 Philippe LeCavalier [this message]
2011-01-29 19:00 ` Tero Tilus
[not found] ` <20110129141920.nfxc8118ysss0840@webmail.plecavalier.com>
2011-01-29 22:46 ` Tero Tilus
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=20110129092038.6798sdxsmc04oko8@webmail.plecavalier.com \
--to=support@plecavalier.com \
--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