Hi Aurelien,
Aurelien Jarno wrote:
> > Hrm, with that patch, autopkgtest fails the test case for #600246,
> > i.e. it seems to reopen the infamous and seemingly non-trivial
> > https://bugs.debian.org/600246 — not sure why though. (Wonder if
> > Thorsten's patch works better for #600246 than the c
Hi Axel,
On 2023-01-05 03:25, Axel Beckert wrote:
> Hi Aurelien,
>
> Axel Beckert wrote:
> > Aurelien Jarno wrote:
> > > An alternative is to not try to support all systems and reinvent the
> > > wheel, and instead assume a POSIX system.
> >
> > I'd say on Debian — independent of the actually us
Hi Aurelien,
Axel Beckert wrote:
> Aurelien Jarno wrote:
> > An alternative is to not try to support all systems and reinvent the
> > wheel, and instead assume a POSIX system.
>
> I'd say on Debian — independent of the actually used kernel — we can
> do assume this at least.
>
> > That way the a
Hi Aurelien,
Aurelien Jarno wrote:
> An alternative is to not try to support all systems and reinvent the
> wheel, and instead assume a POSIX system.
I'd say on Debian — independent of the actually used kernel — we can
do assume this at least.
> That way the attached patch can be used.
Nice pat
On 2023-01-03 13:06:38 +0100, Aurelien Jarno wrote:
> Do you mean having a strict dependency on the major glibc version? That
> sounds like an additional pain for new glibc releases, given how GNU
> screen is developed upstream. And screen has an udeb, so it's not easy
> to remove it from testing i
control: reassign -1 screen
control: retitle -1 GNU Screen does not support Unicode 14
control: affects -1 libc6
Hi,
On 2023-01-03 02:28, Vincent Lefevre wrote:
> On 2023-01-02 23:08:39 +0100, Aurelien Jarno wrote:
> > This U+1FAF6 character is new in Unicode 14, which is supported starting
> > w
Cc'ing Axel Beckert, who maintains screen.
On 2023-01-03 02:28:14 +0100, Vincent Lefevre wrote:
> On 2023-01-02 23:08:39 +0100, Aurelien Jarno wrote:
> > This U+1FAF6 character is new in Unicode 14, which is supported starting
> > with glibc 2.35. Older glibc does not know about this character, ca
On 2023-01-02 23:08:39 +0100, Aurelien Jarno wrote:
> This U+1FAF6 character is new in Unicode 14, which is supported starting
> with glibc 2.35. Older glibc does not know about this character, causing
> mutt to display it with '?'. With newer glibc mutt displays the
> character.
>
> Now I am not
Hi,
On 2023-01-02 16:34, Vincent Lefevre wrote:
> Package: libc6
> Version: 2.36-7
> Severity: serious
>
> The new libc6 appears to have some change related to Unicode that
> yields display issues in screen 4.9.0-3, such as horizontal and/or
> vertical text shifting. A consequence of this text sh
On 2023-01-02 19:08 +0100, Vincent Lefevre wrote:
> On 2023-01-02 18:07:52 +0100, Sven Joachim wrote:
>> On 2023-01-02 16:34 +0100, Vincent Lefevre wrote:
>> > There is no such issue under bullseye (Debian 11.6), which also has
>> > GNU Screen 4.09.00, so the breakage appears to be due to libc6.
>
On 2023-01-02 19:27:28 +0100, Vincent Lefevre wrote:
> Hmm... This also depends on the terminal.
>
> This problem (both step 2 and step 3) is reproducible with xterm,
> rxvt and GNOME Terminal, but not mlterm.
>
> This might also be a terminal bug, but several terminals would be
> affected by the
On 2023-01-02 19:08:17 +0100, Vincent Lefevre wrote:
> > > Example to reproduce the issue with the U+1FAF6 HEART HANDS character
> > > under Debian/unstable:
> > >
> > > 1. Run "screen" in a 80-column terminal.
> > >
> > > 2. Open this mailbox with "mutt -F /dev/null -f heart-hands.mbox".
> > >
On 2023-01-02 18:07:52 +0100, Sven Joachim wrote:
> On 2023-01-02 16:34 +0100, Vincent Lefevre wrote:
> > There is no such issue under bullseye (Debian 11.6), which also has
> > GNU Screen 4.09.00, so the breakage appears to be due to libc6.
>
> Without having looked at the problem: this appears t
On 2023-01-02 16:34 +0100, Vincent Lefevre wrote:
> Package: libc6
> Version: 2.36-7
> Severity: serious
>
> The new libc6 appears to have some change related to Unicode that
> yields display issues in screen 4.9.0-3, such as horizontal and/or
> vertical text shifting. A consequence of this text s
Package: libc6
Version: 2.36-7
Severity: serious
The new libc6 appears to have some change related to Unicode that
yields display issues in screen 4.9.0-3, such as horizontal and/or
vertical text shifting. A consequence of this text shifting is that
in Mutt (in particular with arrow_cursor), one m
15 matches
Mail list logo