all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9496@debbugs.gnu.org
Subject: bug#9496: 24.0.50; Segfault on TAB-only composition
Date: Sat, 04 Feb 2012 15:43:56 -0800	[thread overview]
Message-ID: <4F2DC2BC.9080202@cs.ucla.edu> (raw)
In-Reply-To: <83bopfdnh1.fsf@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.

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's what's done with tabs, so there's good precedent for it.
This would require changes to the rendering code so that it matches
the altered char-width that's ceilinged at 1000.





  reply	other threads:[~2012-02-04 23:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13 20:22 bug#9496: 24.0.50; Segfault on TAB-only composition Johan Bockgård
2011-09-14  5:33 ` Eli Zaretskii
2011-09-14 12:57   ` Kenichi Handa
2011-09-14 13:07     ` Eli Zaretskii
2011-09-15  0:28       ` Kenichi Handa
2011-09-15  0:47         ` Stefan Monnier
2011-09-15  4:10           ` Kenichi Handa
2011-11-11  7:15 ` Kenichi Handa
2012-02-03 19:28 ` Paul Eggert
2012-02-03 21:22   ` Eli Zaretskii
2012-02-03 22:07     ` Paul Eggert
2012-02-04  6:58       ` Eli Zaretskii
2012-02-04  7:18         ` Paul Eggert
2012-02-04  8:14           ` Eli Zaretskii
2012-02-04 23:43             ` Paul Eggert [this message]
2012-02-05 16:36               ` Eli Zaretskii
2012-02-05 16:39                 ` Paul Eggert

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=4F2DC2BC.9080202@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=9496@debbugs.gnu.org \
    --cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.