Variable: denote-history-completion-in-prompts

denote-history-completion-in-prompts is a customizable variable defined in denote.el.

Value

t

Documentation

Toggle history completion in all denote-prompts-with-history-as-completion.

When this user option is set to a non-nil value, use minibuffer history entries as completion candidates in denote-prompts-with-history-as-completion. Those will show previous inputs from their respective history as possible values to select, either to (i) re-insert them verbatim or (ii) with the intent to edit further (depending on the minibuffer user interface, one can select a candidate with TAB without exiting the minibuffer, as opposed to what RET normally does by selecting and exiting).

When this user option is set to a nil value, all of the denote-prompts-with-history-as-completion do not use minibuffer completion: they just prompt for a string of characters. Their history is still available through all the standard ways of retrieving minibuffer history, such as with the command previous-history-element.

History completion still allows arbitrary values to be provided as input: they do not have to match the available minibuffer completion candidates.

Note that some prompts, like denote-keywords-prompt, always use minibuffer completion, due to the specifics of their data.

[ Consider enabling the built-in savehist-mode(var)/savehist-mode(fun) to persist minibuffer
  histories between sessions.]

Also see denote-prompts.

This variable was added, or its default value changed, in denote version 2.3.0.

Source Code

;; Defined in ~/.emacs.d/elpa/denote-4.2.3/denote.el
(defcustom denote-history-completion-in-prompts t
  "Toggle history completion in all `denote-prompts-with-history-as-completion'.

When this user option is set to a non-nil value, use minibuffer history
entries as completion candidates in `denote-prompts-with-history-as-completion'.
Those will show previous inputs from their respective history as
possible values to select, either to (i) re-insert them verbatim or (ii)
with the intent to edit further (depending on the minibuffer user
interface, one can select a candidate with TAB without exiting the
minibuffer, as opposed to what RET normally does by selecting and
exiting).

When this user option is set to a nil value, all of the
`denote-prompts-with-history-as-completion' do not use minibuffer
completion: they just prompt for a string of characters.  Their
history is still available through all the standard ways of retrieving
minibuffer history, such as with the command `previous-history-element'.

History completion still allows arbitrary values to be provided as
input: they do not have to match the available minibuffer completion
candidates.

Note that some prompts, like `denote-keywords-prompt', always use
minibuffer completion, due to the specifics of their data.

[ Consider enabling the built-in `savehist-mode' to persist minibuffer
  histories between sessions.]

Also see `denote-prompts'."
  :type 'boolean
  :package-version '(denote . "2.3.0")
  :group 'denote)