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: 39529@debbugs.gnu.org, federicotedin@gmail.com
Subject: bug#39529: 28.0.50; Metahelp does not contain help text
Date: Sun, 16 Feb 2020 17:35:43 +0200	[thread overview]
Message-ID: <83pneemto0.fsf@gnu.org> (raw)
In-Reply-To: <e1dae7d6-376c-a9f5-b0b6-4ade20dca59b@cs.ucla.edu> (message from Paul Eggert on Sat, 15 Feb 2020 15:25:44 -0800)

> Cc: federicotedin@gmail.com, 39529-done@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sat, 15 Feb 2020 15:25:44 -0800
> 
> > I suspect the sxhash changes on Jan 7.  This problem started happening
> > in that day's build.
> 
> Right you are. The problem was Emacs was using a hash table to unify identical 
> Lisp compiled objects when purecopying them, even though their doc strings were 
> not set up yet (and so were 0 placeholders that always compared equal). Formerly 
> this bug was masked because sxhash simply returned the objects' hashed 
> addresses, but the January 7 changes unveiled the bug. I install the attached 
> patch to fix the problem.

Thanks, the problem is gone now.





  reply	other threads:[~2020-02-16 15:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09 19:06 bug#39529: 28.0.50; Metahelp does not contain help text Federico Tedin
2020-02-09 19:22 ` Eli Zaretskii
2020-02-09 19:34   ` Eli Zaretskii
2020-02-15 23:25     ` Paul Eggert
2020-02-16 15:35       ` Eli Zaretskii [this message]
2020-02-16 16:51       ` Pip Cet
2020-02-16 19:43         ` Paul Eggert
2020-02-18 19:56           ` Pip Cet
2020-02-19  1:21             ` Paul Eggert
2020-02-19  2:34               ` Pip Cet
2020-02-19  9:00                 ` 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=83pneemto0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39529@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=federicotedin@gmail.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 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.