[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#9496: 24.0.50; Segfault on TAB-only composition
From: |
Eli Zaretskii |
Subject: |
bug#9496: 24.0.50; Segfault on TAB-only composition |
Date: |
Sun, 05 Feb 2012 18:36:30 +0200 |
> Date: Sat, 04 Feb 2012 15:43:56 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: 9496@debbugs.gnu.org
>
> On 02/04/2012 12:14 AM, Eli Zaretskii wrote:
> > It would be a much better solution if char_width would limit the
> > result to the same sane limit we have in all the related functions and
> > macros, i.e. to 1000.
>
> OK, that's doable, but if done in isolation it would introduce other
> bugs, no? If char-width returns a value that's arbitrarily ceilinged
> at 1000, but actual characters can be wider than 1000 columns,
> code that uses char-width to count columns will be buggy.
How can an actual character (not its display-table replacement) be
wider than that?
> We could address this by changing the code that renders characters,
> so that the code limits them to at most 1000 columns on the display.
That was my intent, yes.
- bug#9496: 24.0.50; Segfault on TAB-only composition, Paul Eggert, 2012/02/03
- bug#9496: 24.0.50; Segfault on TAB-only composition, Eli Zaretskii, 2012/02/03
- bug#9496: 24.0.50; Segfault on TAB-only composition, Paul Eggert, 2012/02/03
- bug#9496: 24.0.50; Segfault on TAB-only composition, Eli Zaretskii, 2012/02/04
- bug#9496: 24.0.50; Segfault on TAB-only composition, Paul Eggert, 2012/02/04
- bug#9496: 24.0.50; Segfault on TAB-only composition, Eli Zaretskii, 2012/02/04
- bug#9496: 24.0.50; Segfault on TAB-only composition, Paul Eggert, 2012/02/04
- bug#9496: 24.0.50; Segfault on TAB-only composition,
Eli Zaretskii <=
- bug#9496: 24.0.50; Segfault on TAB-only composition, Paul Eggert, 2012/02/05