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, Drew Adams <drew.adams@oracle.com>
Subject: bug#58786: 29.0.50; Error with Info-minibuf-history not declared
Date: Wed, 26 Oct 2022 20:21:13 +0000	[thread overview]
Message-ID: <877d0me3p8.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmkNEseCgaC-=+tzG2=-hrYrutHKRTcmbT-NNCYxBVR4uw@mail.gmail.com>

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


Stefan Kangas <stefankangas@gmail.com> writes:

> close 58786 29.1
> thanks
>
> Thierry Volpiatto <thievol@posteo.net> writes:
>
>> Drew Adams <drew.adams@oracle.com> writes:
>>
>>> My code includes just a vacuous defvar, to
>>> declare the var but not initialize it to nil.
>>>
>>>   (defvar Info-minibuf-history)
>>
>> You should not have to do this, this defvar should be in info.el on top
>> of file ideally.  Initialized to nil or not I don't know, but it should
>> be declared anyway.
>> I personally initialize these history vars to nil in all my packages.
>
> I've now declared it (commit 68548af68a), and I'm closing this bug.

Thanks.

-- 
Thierry

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

      reply	other threads:[~2022-10-26 20:21 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
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 [this message]

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=877d0me3p8.fsf@posteo.net \
    --to=thievol@posteo.net \
    --cc=58786@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --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.