unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 48019@debbugs.gnu.org
Subject: bug#48019: 28.0.50; Error signaled by documentation function
Date: Tue, 27 Apr 2021 20:07:01 +0300	[thread overview]
Message-ID: <878s53psga.fsf@mail.linkov.net> (raw)
In-Reply-To: <87h7js7ghy.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 27 Apr 2021 01:50:17 +0200")

>> Using help commands to get docstrings from the etc/DOC file
>> raises an error, e.g. on typing 'C-h m':
>>
>>   Debugger entered--Lisp error: (wrong-type-argument listp t)
>>     documentation(auto-composition-mode)
>>     describe-mode()
>>     funcall-interactively(describe-mode)
>>     call-interactively(describe-mode nil nil)
>>     command-execute(describe-mode)
>>
>> This is a recent regression.
>
> I saw similar problems just now (not with `C-h m', but eldoc calling
> `documentation' with parameters that made it bug out).  I did a "make
> bootstrap", and I'm no longer seeing those problems.
>
> If you do the same, does the problem go away for you, too?

No need to make bootstrap.  It should be enough just to restart Emacs.
So the problem is the need to restart Emacs every time after compilation.
Actually, not after every compilation, but I can't determine on what
condition this error depends.  This is a new regression appeared
in the last 2 weeks.  Before some recent change, there was no need
to restart Emacs after compilation.





  reply	other threads:[~2021-04-27 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25 17:13 bug#48019: 28.0.50; Error signaled by documentation function Juri Linkov
2021-04-26 23:50 ` Lars Ingebrigtsen
2021-04-27 17:07   ` Juri Linkov [this message]
2021-04-27 23:27     ` Lars Ingebrigtsen
2021-04-27 23:59       ` Lars Ingebrigtsen
2021-04-28  0:02       ` Lars Ingebrigtsen
2021-04-29 22:13         ` Stefan Monnier
2021-05-02  8:51           ` 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=878s53psga.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=48019@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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).