minibuffer history positions - 0 or 1 based?

minibuffer history positions - 0 or 1 based?

[Ian Zimmerman]

Info:

(VARIABLE . STARTPOS)
     Use VARIABLE (a symbol) as the history list, and assume that the
     initial history position is STARTPOS (an integer, counting from
     zero which specifies the most recent element of the history).

Docstring:

  It can be a symbol, which is the history list variable to use,
  or it can be a cons cell (HISTVAR . HISTPOS).
  In that case, HISTVAR is the history list variable to use,
  and HISTPOS is the initial position (the position in the list
  which INITIAL-CONTENTS corresponds to).
  Positions are counted starting from 1 at the beginning of the list.


Which is it?  And is this a known documentation bug?

-- 
A true pessimist won't be discouraged by a little success.

Re: minibuffer history positions - 0 or 1 based?

[Eli Zaretskii]

> From: Ian Zimmerman <nobrowser@gmail.com>
> Date: Thu, 10 Nov 2005 21:13:02 -0800 (PST)
> 
> Info:
> 
> (VARIABLE . STARTPOS)
>      Use VARIABLE (a symbol) as the history list, and assume that the
>      initial history position is STARTPOS (an integer, counting from
>      zero which specifies the most recent element of the history).

In the current development sources, this fragment was changed to say:

    (VARIABLE . STARTPOS)
	 Use VARIABLE (a symbol) as the history list, and assume that the
	 initial history position is STARTPOS (a nonnegative integer).

	 Specifying 0 for STARTPOS is equivalent to just specifying the
	 symbol VARIABLE.  `previous-history-element' will display the most
	 recent element of the history list in the minibuffer.  If you
	 specify a positive STARTPOS, the minibuffer history functions
	 behave as if `(elt VARIABLE (1- STARTPOS))' were the history
	 element currently shown in the minibuffer.

> Which is it?  And is this a known documentation bug?

Does the above answers your question?

Re: minibuffer history positions - 0 or 1 based?

[Ian Zimmerman]

Eli> In the current development sources, this fragment was changed to
Eli> say:

Eli>     (VARIABLE . STARTPOS) Use VARIABLE (a symbol) as the history
Eli> list, and assume that the initial history position is STARTPOS (a
Eli> nonnegative integer).

Eli> 	 Specifying 0 for STARTPOS is equivalent to just specifying the
Eli> symbol VARIABLE.  `previous-history-element' will display the most
Eli> recent element of the history list in the minibuffer.  If you
Eli> specify a positive STARTPOS, the minibuffer history functions
Eli> behave as if `(elt VARIABLE (1- STARTPOS))' were the history
Eli> element currently shown in the minibuffer.

Eli> Does the above answers your question?

Yes, thanks.

-- 
A true pessimist won't be discouraged by a little success.