unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thievol@posteo.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: "58786@debbugs.gnu.org" <58786@debbugs.gnu.org>,
	Stefan Kangas <stefankangas@gmail.com>
Subject: bug#58786: 29.0.50; Error with Info-minibuf-history not declared
Date: Wed, 26 Oct 2022 17:03:09 +0000	[thread overview]
Message-ID: <87pmeezf33.fsf@posteo.net> (raw)
In-Reply-To: <CO6PR10MB5473AE435EEE56E3792E80D6F3309@CO6PR10MB5473.namprd10.prod.outlook.com>

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


Hello Drew,

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. 

> That works, and in all Emacs versions, AFAIK.

AFAIK this variable is not used in previous emacs versions.

-- 
Thierry

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

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

  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=87pmeezf33.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 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).