bug#2866: 23.0.91; "(princ (category-table) (current-buffer))" causes emacs to hang

bug#2866: 23.0.91; "(princ (category-table) (current-buffer))" causes emacs to hang

[MON KEY]

evaluating:
(princ (category-table) (current-buffer))
Causes emacs to hang.

Whether this is a useful way to examine the category-table is another
question entirely :P

I've evaluated the previous expression on two separate builds with
identical (undesirable) results:
---
GNU Emacs 23.0.91.1 (i386-mingw-nt5.1.2600)  of 2009-02-26 on SOFT-MJASON
---
GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-10-23 on
LENNART-69DE564 (patched)
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --cflags -Ic:/g/include'
---
;;; ==============================
In GNU Emacs 23.0.91.1 (i386-mingw-nt5.1.2600)
 of 2009-02-26 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: ENU
  value of $XMODIFIERS: nil
  locale-coding-system: cp1252
  default-enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
  show-paren-mode: t
  display-time-mode: t
  auto-image-file-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  size-indication-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t

bug#2866: 23.0.91; "(princ (category-table) (current-buffer))" causes emacs to hang

[Kenichi Handa]

In article <d2afcfda0904021236i40758ef4vd17c4fb97e31d67f@mail.gmail.com>, MON KEY <monkey@sandpframing.com> writes:

> evaluating:
> (princ (category-table) (current-buffer))
> Causes emacs to hang.

> Whether this is a useful way to examine the category-table is another
> question entirely :P

It doesn't hang Emacs for me but takes long time in
redisplay.  It's because of the extremely long line.

If it is ok to terminate lines within the printing of a
object, something like this change will speed up the
redisplay.

--- print.c.~1.255.~	2009-01-16 15:52:25.000000000 +0900
+++ print.c	2009-04-03 10:44:14.000000000 +0900
@@ -2116,6 +2116,9 @@
 	      /* We print a char-table as if it were a vector,
 		 lumping the parent and default slots in with the
 		 character slots.  But we add #^ as a prefix.  */
+	      if (SUB_CHAR_TABLE_P (obj)
+		  && XINT (XSUB_CHAR_TABLE (obj)->depth) == 3)
+		PRINTCHAR ('\n');
 	      PRINTCHAR ('#');
 	      PRINTCHAR ('^');
 	      if (SUB_CHAR_TABLE_P (obj))

---
Kenichi Handa
handa@m17n.org

bug#2866: 23.0.91; "(princ (category-table) (current-buffer))" causes emacs to hang

[Stefan Monnier]

>> evaluating:
>> (princ (category-table) (current-buffer))
>> Causes emacs to hang.

>> Whether this is a useful way to examine the category-table is another
>> question entirely :P

> It doesn't hang Emacs for me but takes long time in
> redisplay.  It's because of the extremely long line.

> If it is ok to terminate lines within the printing of a
> object, something like this change will speed up the
> redisplay.

Looks like a good quick-fix.  Better of course would be to speed up the
(re)display of long lines.


        Stefan

bug#2866: 23.0.91; "(princ (category-table) (current-buffer))" causes emacs to hang

[Kenichi Handa]

In article <jwv1vsa5st7.fsf-monnier+emacsbugreports@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> evaluating:
>>> (princ (category-table) (current-buffer))
>>> Causes emacs to hang.

>>> Whether this is a useful way to examine the category-table is another
>>> question entirely :P

> > It doesn't hang Emacs for me but takes long time in
> > redisplay.  It's because of the extremely long line.

> > If it is ok to terminate lines within the printing of a
> > object, something like this change will speed up the
> > redisplay.

> Looks like a good quick-fix.

I've just installed it.

> Better of course would be to speed up the (re)display of
> long lines.

Sure.

---
Kenichi Handa
handa@m17n.org