all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 9496@debbugs.gnu.org
Subject: bug#9496: 24.0.50; Segfault on TAB-only composition
Date: Sat, 04 Feb 2012 10:14:34 +0200	[thread overview]
Message-ID: <83bopfdnh1.fsf@gnu.org> (raw)
In-Reply-To: <4F2CDBDA.6080307@cs.ucla.edu>

> Date: Fri, 03 Feb 2012 23:18:50 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
> 
> On 02/03/2012 10:58 PM, Eli Zaretskii wrote:
> > Then don't do that.
> 
> I don't see why not.

Because the result is meaningless anyway.  Being able to "express" a
2G column wide "character" is not useful, so avoiding overflow for
that use case is not really a solution to the problem.

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.  If you limit everything in that function to
1000, including its result, there's no danger of overflow anywhere,
and the resulting display is not too preposterous.





  reply	other threads:[~2012-02-04  8:14 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 [this message]
2012-02-04 23:43             ` Paul Eggert
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=83bopfdnh1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=9496@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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.