all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 63881@debbugs.gnu.org
Subject: bug#63881: 29.0.91; apropos-documentation fails when load-history contains element whose CAR is nil
Date: Sun, 04 Jun 2023 14:04:06 +0530	[thread overview]
Message-ID: <655658B8-D58D-4D1B-80F4-33A1A200B417@gmail.com> (raw)
In-Reply-To: <83cz2b7pyp.fsf@gnu.org>



On 4 June 2023 11:01:58 GMT+05:30, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Visuwesh <visuweshm@gmail.com>
>> Date: Sun, 04 Jun 2023 08:37:08 +0530
>> 
>> 
>> As per (info "(elisp) Where Defined"), load-history may contain an
>> element whose CAR is nil if eval-buffer was used to evaluate a defun
>> in a non-file-visiting buffer.
>> 
>> After such an entry is added to load-history, apropos-documentation
>> fails with the backtrace at end.
>
>How did you add such an entry to load-history?  IOW, is there a
>real-life use case where this happens?

eval-buffer is the answer apparently.  I don't remember using the command explicitly myself though so some other eval command is calling it.
Also see the reproducer below.

>> To reproduce the issue,
>> 
>>     1. emacs -Q
>>     2. Insert (defun test () t)
>>     3. M-x eval-buffer RET
>>     4. Confirm that a nil entry is present in load-history by evaluating
>>        (alist-get nil load-history 'none)
>>     5. C-h d any RET





  reply	other threads:[~2023-06-04  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-04  3:07 bug#63881: 29.0.91; apropos-documentation fails when load-history contains element whose CAR is nil Visuwesh
2023-06-04  5:31 ` Eli Zaretskii
2023-06-04  8:34   ` Visuwesh [this message]
2023-06-05  7:50   ` Matt Beshara
2023-06-10  9:25   ` Eli Zaretskii
2023-06-10 16:18     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-10 17:49       ` Eli Zaretskii

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=655658B8-D58D-4D1B-80F4-33A1A200B417@gmail.com \
    --to=visuweshm@gmail.com \
    --cc=63881@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.