* minibuffer history positions - 0 or 1 based?
@ 2005-11-11 5:13 Ian Zimmerman
2005-11-11 9:43 ` Eli Zaretskii
0 siblings, 1 reply; 3+ messages in thread
From: Ian Zimmerman @ 2005-11-11 5:13 UTC (permalink / raw)
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: minibuffer history positions - 0 or 1 based?
2005-11-11 5:13 minibuffer history positions - 0 or 1 based? Ian Zimmerman
@ 2005-11-11 9:43 ` Eli Zaretskii
2005-11-12 14:19 ` Ian Zimmerman
0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2005-11-11 9:43 UTC (permalink / raw)
> 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?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: minibuffer history positions - 0 or 1 based?
2005-11-11 9:43 ` Eli Zaretskii
@ 2005-11-12 14:19 ` Ian Zimmerman
0 siblings, 0 replies; 3+ messages in thread
From: Ian Zimmerman @ 2005-11-12 14:19 UTC (permalink / raw)
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-11-12 14:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-11-11 5:13 minibuffer history positions - 0 or 1 based? Ian Zimmerman
2005-11-11 9:43 ` Eli Zaretskii
2005-11-12 14:19 ` Ian Zimmerman
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).