From: Michael Hamann <michael@content-space.de>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] utf-8 script encoding
Date: Sat, 13 Feb 2010 14:51:53 +0100 [thread overview]
Message-ID: <1266066673-sup-5419@mithink> (raw)
In-Reply-To: <1264250655-sup-3062@masanjin.net>
Hi,
Excerpts from William Morgan's message of 2010-01-23 13:44:39 +0100:
> Reformatted excerpts from Gaute Hope's message of 2010-01-03:
> > No. Tab completion fails, and sending fails, I can add names with
> > UTF-8 chars to the recipient list, but it fails with the last attached
> > exception. This is the same behaviour as earlier.
>
> That's weird, I would've expected this to help. What's the alternative,
> adding "u" to the end of every regexp?
Has there been any progress on this subject? This is imho a quite annoying bug
as it makes me regularly recover mails from the buffer of screen when having
written a reply to a message with a subject containing utf-8 chars without
noticing that.
Sorry if this should have been fixed already, I'm currently using git next and
there the problem still exists.
Greetings
Michael Hamann
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-02-13 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 14:02 [sup-devel] [issue36] label tab completion with utf-8 chars fail Gaute Hope
2010-01-03 15:51 ` Gaute Hope
2010-01-03 15:56 ` Gaute Hope
2010-01-15 10:23 ` Gaute Hope
2010-01-03 16:07 ` [PATCH] utf-8 script encoding Rich Lane
2010-01-03 16:18 ` Gaute Hope
2010-01-23 12:44 ` [sup-devel] " William Morgan
2010-02-13 13:51 ` Michael Hamann [this message]
2010-09-09 12:02 ` Gaute Hope
2010-09-17 10:54 ` Gaute Hope
2010-10-04 8:40 ` Gaute Hope
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=1266066673-sup-5419@mithink \
--to=michael@content-space.de \
--cc=sup-devel@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