all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Thierry Volpiatto <thievol@posteo.net>,
	Stefan Kangas <stefankangas@gmail.com>
Cc: "58786@debbugs.gnu.org" <58786@debbugs.gnu.org>
Subject: bug#58786: 29.0.50; Error with Info-minibuf-history not declared
Date: Wed, 26 Oct 2022 16:11:27 +0000	[thread overview]
Message-ID: <CO6PR10MB5473AE435EEE56E3792E80D6F3309@CO6PR10MB5473.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87mt9jj6t1.fsf@posteo.net>

My code includes just a vacuous defvar, to
declare the var but not initialize it to nil.

  (defvar Info-minibuf-history)

That works, and in all Emacs versions, AFAIK.

On the other hand, we still have this in the
Elisp manual, node `Minibuffer History'.  It
says that you must initialize a history var
to nil.  I don't think that's correct (and I
don't think that should be needed).

   If you don't specify HISTORY, then the
   default history list 'minibuffer-history'
   is used.  For other standard history lists,
   see below.  You can also create your own
   history list variable; just initialize it
   to 'nil' before the first use.

I think the last sentence can/should be
changed to tell users to declare the var,
not that they need to initialize it to nil.





  reply	other threads:[~2022-10-26 16:11 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 [this message]
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=CO6PR10MB5473AE435EEE56E3792E80D6F3309@CO6PR10MB5473.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=58786@debbugs.gnu.org \
    --cc=stefankangas@gmail.com \
    --cc=thievol@posteo.net \
    /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.