From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] System encoding versus messages encoding
Date: Tue, 22 Apr 2008 19:03:07 -0700 [thread overview]
Message-ID: <1208916152-sup-4053@south> (raw)
In-Reply-To: <1208908666-sup-5839@elly>
Reformatted excerpts from Israel Herraiz's message of 2008-04-22:
> I am noting only another odd thing: when I press enter to from the
> inbox-mode to the thread-mode, some characters of the inbox view
> "persists" in the screen.
Yeah, I see this too. Looks like a string length issue, actually.
I'll look into it---probably an easy fix.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-04-23 2:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 20:37 Israel Herraiz
2008-04-22 11:39 ` Shot (Piotr Szotkowski)
2008-04-22 23:18 ` William Morgan
2008-04-23 0:09 ` Israel Herraiz
2008-04-23 2:03 ` William Morgan [this message]
2008-04-23 1:08 ` Israel Herraiz
2008-04-23 1:53 ` William Morgan
2008-04-24 19:36 ` Marc Hartstein
2008-04-24 23:10 ` [sup-talk] [PATCH] fixed dlopen of libc for os x Grant Hollingworth
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=1208916152-sup-4053@south \
--to=wmorgan-sup@masanjin.net \
/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