unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Norm Tovey-Walsh <ndw@nwalsh.com>, 48135@debbugs.gnu.org
Subject: bug#48135: 27.1.91; standard-display-table incorrectly initialized in byte compiled code?
Date: Sat, 01 May 2021 12:00:27 +0000	[thread overview]
Message-ID: <4edb14352660e56af8c0@heytings.org> (raw)
In-Reply-To: <835z02adnw.fsf@gnu.org>


>> Now byte compile the file and start emacs: emacs -q -l testdt.elc
>>
>> You'll get a wrong-type-argument error and the *Messages* buffer will 
>> contain:
>>
>>   For information about GNU Emacs and the GNU system, type C-h C-a.
>>   Hello
>>   display-table-slot: Wrong type argument: char-table-p, nil
>>
>> The *Help* buffer will contain:
>>
>>   Truncation glyph:
>>
>> Apparently, there's something wrong with attempting to access the 
>> standard-display-table from byte compiled code.
>
> I cannot reproduce this with the stock version of Emacs 27.2 (of which 
> yours seems to be a pretest).  I get the same results from both the 
> compiled and the interpreted versions.
>

Perhaps it's a GNU/Linux specific bug, but I can reproduce this with Emacs 
22-28.  It worked with Emacs 21.  standard-display-table is nil before 
invoking describe-display-table, and somehow becomes populated when 
discribe-display-table is invoked from a non-byte-compiled file, but not 
when it is invoked from a byte-compiled file.  A simple workaround is to 
(require 'disp-table).





  reply	other threads:[~2021-05-01 12:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01  8:16 bug#48135: 27.1.91; standard-display-table incorrectly initialized in byte compiled code? Norm Tovey-Walsh
2021-05-01 11:36 ` Eli Zaretskii
2021-05-01 12:00   ` Gregory Heytings [this message]
2021-05-01 12:16     ` Eli Zaretskii
2021-05-01 12:22       ` Gregory Heytings
2021-05-01 13:07     ` Norm Tovey-Walsh
2021-05-02  7:12       ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4edb14352660e56af8c0@heytings.org \
    --to=gregory@heytings.org \
    --cc=48135@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=ndw@nwalsh.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).