all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thievol@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 58786@debbugs.gnu.org
Subject: bug#58786: 29.0.50; Error with Info-minibuf-history not declared
Date: Wed, 26 Oct 2022 08:45:13 +0000	[thread overview]
Message-ID: <87r0yvj76a.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmkDTjuqQMyhSt0DcZ9rWmWQu=oztYLUFRQPOGjU+4Pzbw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]


Stefan Kangas <stefankangas@gmail.com> writes:

> Thierry Volpiatto <thievol@posteo.net> writes:
>
>>> Do you have a recipe to reproduce this bug, starting from "emacs -Q"?
>>
>> I could reproduce from emacs -Q as described previously.
>
> I couldn't reproduce it using this recipe:
>
> 0. emacs -Q
> 1. C-h i g
>
> Are there any other steps required to reproduce it?

I can't reproduce anymore now.
I think vanilla Emacs completing-read fails silently when an history var
is not initialized (correct me if I am wrong) i.e. it behave just like
if it were not defined.

But, do you agree that code using completing-read with an history
variable should declare this var?

If not could you please explain me how such an history variable is defined, loaded etc...

Here we have:

    (completing-read prompt #'Info-read-node-name-1 nil t nil
                            'Info-minibuf-history default)

and Info-minibuf-history is defvared nowhere.
Could you please fix it?

-- 
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]

  reply	other threads:[~2022-10-26  8:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26  3:48 bug#58786: 29.0.50; Error with Info-minibuf-history not declared Thierry Volpiatto
2022-10-26  5:36 ` Stefan Kangas
2022-10-26  6:02   ` Thierry Volpiatto
2022-10-26  6:38     ` Stefan Kangas
2022-10-26  8:45       ` Thierry Volpiatto [this message]
2022-10-26  9:00         ` Thierry Volpiatto
2022-10-26 16:11           ` Drew Adams
2022-10-26 17:03             ` Thierry Volpiatto
2022-10-26 18:40               ` Drew Adams
2022-10-26 19:21               ` Stefan Kangas
2022-10-26 20:21                 ` Thierry Volpiatto

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=87r0yvj76a.fsf@posteo.net \
    --to=thievol@posteo.net \
    --cc=58786@debbugs.gnu.org \
    --cc=stefankangas@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.