| From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Marko Kreen <markokr(at)gmail(dot)com>, Martin Pitt <mpitt(at)debian(dot)org>, Markus Wanner <markus(at)bluegap(dot)ch>, jd(at)commandprompt(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Debian readline/libedit breakage |
| Date: | 2011-02-15 17:52:04 |
| Message-ID: | 4D5ABD44.7020507@kaltenbrunner.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/15/2011 12:37 PM, Greg Stark wrote:
> On Tue, Feb 15, 2011 at 6:12 AM, Stefan Kaltenbrunner
> <stefan(at)kaltenbrunner(dot)cc> wrote:
>> from what I can see upstream libedit actually has utf8 support for a while
>> now (as well as some other fixes) but the debian libedit version (and also
>> the one of other distributions) is way too old for that so maybe most of the
>> issues would be mood if debian updated to a newer libedit version...
>
> There's utf8 support and then there's utf8 support. last I saw libedit
> didn't actually stop you from using utf8 and things kind of worked,
> but none of the editing commands understand what the multibyte
> characters were or understood what column position you were in so you
> could easily end up deleting half a character or with the insertion
> point in the middle of a character.
well I have not actually tested - I was just reading the changelog on
http://www.thrysoee.dk/editline/ which claims UTF8 "support" (whatever
that means) in the current code drop.
Stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-02-15 17:52:14 | Re: XMin Hot Standby Feedback patch |
| Previous Message | Tom Lane | 2011-02-15 17:51:31 | Re: Fix for Index Advisor related hooks |