[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lispref on history-add-new-input
From: |
Eli Zaretskii |
Subject: |
Re: Lispref on history-add-new-input |
Date: |
Fri, 02 Jun 2006 13:49:07 +0300 |
> From: Juri Linkov <address@hidden>
> Date: Fri, 02 Jun 2006 12:29:32 +0300
> Cc: address@hidden, address@hidden
>
> > @defvar history-add-new-input
> > ! If the value of this variable is @code{nil}, standard functions that
> > ! read from the minibuffer don't add new elements to the history list,
> >
> > It would be clearer to break the sentence here.
> >
> > ! allowing code to explicitly manage the history by using
> > ! @code{add-to-history}.
>
> The main purpose of this variable was to allow Lisp code to use
> add-to-history after reading an input. In the Info documentation
> the description of this variable goes just after the description
> of add-to-history, so there could be some text that connects these two.
This might be a misunderstanding. Perhaps Richard wasn't suggesting
to remove that part, but instead rephrase like this:
@defvar history-add-new-input
If the value of this variable is @code{nil}, standard functions that
read from the minibuffer don't add new elements to the history list.
This lets Lisp programs explicitly manage input history by using
@code{add-to-history}.