GNU bug report logs - #31459
25.3; Uninitialised unicode-property-table-internal

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 31459 in the body.
You can then email your comments to 31459 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Peter" <craven <at> gmx.net>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.3; Uninitialised unicode-property-table-internal
Date: Tue, 15 May 2018 10:50:54 +0200

I've run into the following bug with Emacs GNU Emacs 25.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.26) of 2018-02-09:

When starting up a new Emacs with `emacs -Q', running the following elisp results in garbage:

(let ((names (unicode-property-table-internal 'name)))
  (message "%s" (get-unicode-property-internal names #x1f600))
  ;; grinning face emoji, should return "GRINNING FACE"
  )

This does not in fact show "GRINNING FACE", but what seems like a random
string, e.g. (after string-to-list):
(0 1805 140 1 3 534 447 0 140 3 1804 64 1314 0 534 140 3 104 429 1 85 9 534 447 1 104 1279 1056 2 1803 6 266 447 1 58 3455 1 52 1802 0 1801 140 0 534 140 3 534 447 0 140 3454 3453 1302 0 1800 140 0 534 140 3 314 6 672 447 1 55 1811 0 3452 46 46 46 46)

*After* I run M-x counsel-unicode-char, things work fine.

It seems that the unicode property table is somehow uninitialised initially, and gets initialised by something that counsel-unicode-char does. Is there a way I can run this initialisation myself? I've looked at the elisp and C sources, but haven't been able to find what I'm doing incorrectly here :-/

Thanks for any help with this!

Greetings, Peter



In GNU Emacs 25.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.26)
 of 2018-02-09 built on bisson
Windowing system distributor 'The X.Org Foundation', version 11.0.11906000
Configured using:
 'configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib
 --localstatedir=/var --with-x-toolkit=gtk3 --with-xft --with-modules
 'CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong
 -fno-plt' CPPFLAGS=-D_FORTIFY_SOURCE=2
 LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now'

Configured features:
XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GCONF GSETTINGS
NOTIFY ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB
TOOLKIT_SCROLL_BARS GTK3 X11 MODULES

Important settings:
  value of $LANG: en_GB.UTF-8
  locale-coding-system: utf-8-unix

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: bug-gnu-emacs <at> gnu.org,Peter <craven <at> gmx.net>,31459 <at> debbugs.gnu.org
Subject: Re: bug#31459: 25.3; Uninitialised unicode-property-table-internal
Date: Tue, 15 May 2018 12:34:36 +0300

On May 15, 2018 11:50:54 AM GMT+03:00, Peter <craven <at> gmx.net> wrote:
> I've run into the following bug with Emacs GNU Emacs 25.3.1
> (x86_64-pc-linux-gnu, GTK+ Version 3.22.26) of 2018-02-09:
> 
> When starting up a new Emacs with `emacs -Q', running the following
> elisp results in garbage:
> 
> (let ((names (unicode-property-table-internal 'name)))
>   (message "%s" (get-unicode-property-internal names #x1f600))
>   ;; grinning face emoji, should return "GRINNING FACE"
>   )
> 
> This does not in fact show "GRINNING FACE", but what seems like a
> random
> string, e.g. (after string-to-list):
> (0 1805 140 1 3 534 447 0 140 3 1804 64 1314 0 534 140 3 104 429 1 85
> 9 534 447 1 104 1279 1056 2 1803 6 266 447 1 58 3455 1 52 1802 0 1801
> 140 0 534 140 3 534 447 0 140 3454 3453 1302 0 1800 140 0 534 140 3
> 314 6 672 447 1 55 1811 0 3452 46 46 46 46)
> 
> *After* I run M-x counsel-unicode-char, things work fine.
> 
> It seems that the unicode property table is somehow uninitialised
> initially, and gets initialised by something that counsel-unicode-char
> does. Is there a way I can run this initialisation myself? I've looked
> at the elisp and C sources, but haven't been able to find what I'm
> doing incorrectly here :-/
> 
> Thanks for any help with this!
> 
> Greetings, Peter
> 
> 
> 
> In GNU Emacs 25.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.26)
>  of 2018-02-09 built on bisson
> Windowing system distributor 'The X.Org Foundation', version
> 11.0.11906000
> Configured using:
>  'configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib
>  --localstatedir=/var --with-x-toolkit=gtk3 --with-xft --with-modules
> 'CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe
> -fstack-protector-strong
>  -fno-plt' CPPFLAGS=-D_FORTIFY_SOURCE=2
>  LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now'
> 
> Configured features:
> XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GCONF GSETTINGS
> NOTIFY ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB
> TOOLKIT_SCROLL_BARS GTK3 X11 MODULES
> 
> Important settings:
>   value of $LANG: en_GB.UTF-8
>   locale-coding-system: utf-8-unix

Why are you using an internal function instead of get-char-code-property?

Message #14 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Peter" <craven <at> gmx.net>
To: Eli Zaretskii <eliz <at> gnu.org>, bug-gnu-emacs <at> gnu.org, 31459 <at> debbugs.gnu.org
Subject: Re: bug#31459: 25.3; Uninitialised unicode-property-table-internal
Date: Tue, 15 May 2018 20:42:33 +0200

Hello Eli!

> Why are you using an internal function instead of get-char-code-property?

Sorry about this, that's entirely due to my ignorance of that function.
I've fixed my code, everything works fine now. Thanks for pointing me
towards the correct function and sorry for wasting your time :-/

Greetings, Peter

Message #22 received at 31459-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: "Peter" <craven <at> gmx.net>
Cc: 31459-done <at> debbugs.gnu.org
Subject: Re: bug#31459: 25.3; Uninitialised unicode-property-table-internal
Date: Tue, 15 May 2018 22:02:04 +0300

> From: "Peter" <craven <at> gmx.net>
> Date: Tue, 15 May 2018 20:42:33 +0200
> 
> > Why are you using an internal function instead of get-char-code-property?
> 
> Sorry about this, that's entirely due to my ignorance of that function.
> I've fixed my code, everything works fine now. Thanks for pointing me
> towards the correct function and sorry for wasting your time :-/

No need to apologize.  I'm closing the bug, then.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.