emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] Changes to emacs/lispref/minibuf.texi


From: Richard M. Stallman
Subject: [Emacs-diffs] Changes to emacs/lispref/minibuf.texi
Date: Mon, 14 Jul 2003 11:55:32 -0400

Index: emacs/lispref/minibuf.texi
diff -c emacs/lispref/minibuf.texi:1.34 emacs/lispref/minibuf.texi:1.35
*** emacs/lispref/minibuf.texi:1.34     Mon Jun 30 06:41:12 2003
--- emacs/lispref/minibuf.texi  Mon Jul 14 11:55:32 2003
***************
*** 84,90 ****
  
  @item
  @code{minibuffer-local-ns-map} is similar, except that @key{SPC} exits
! just like @key{RET}.  This is used mainly for Mocklisp compatibility.
  
  @item
  @code{minibuffer-local-completion-map} is for permissive completion.
--- 84,90 ----
  
  @item
  @code{minibuffer-local-ns-map} is similar, except that @key{SPC} exits
! just like @key{RET}.
  
  @item
  @code{minibuffer-local-completion-map} is for permissive completion.
***************
*** 520,526 ****
  * High-Level Completion::  Convenient special cases of completion
                               (reading buffer name, file name, etc.)
  * Reading File Names::     Using completion to read file names.
! * Programmed Completion::  Finding the completions for a given file name.
  @end menu
  
  @node Basic Completion
--- 520,526 ----
  * High-Level Completion::  Convenient special cases of completion
                               (reading buffer name, file name, etc.)
  * Reading File Names::     Using completion to read file names.
! * Programmed Completion::  Writing your own completion-function.
  @end menu
  
  @node Basic Completion
***************
*** 662,667 ****
--- 662,683 ----
  address@hidden, Emacs does not consider case significant in completion.
  @end defvar
  
+ @defmac lazy-completion-table var fun &rest args
+ This macro provides a way to initialize the variable @var{var} as a
+ completion table in a lazy way, not computing its actual contents
+ until they are first needed.  You use this macro to produce a value
+ that you store in @var{var}.  The actual computation of the proper
+ value is done the first time you do completion using @var{var}.  It is
+ done by calling @var{fun} with the arguments @var{args}.  The value
+ @var{fun} returns becomes the permanent value of @var{var}.
+ 
+ @example
+ (defvar foo (lazy-completion-table foo make-my-alist 'global))
+ (make-local-variable 'bar)
+ (setq bar (lazy-completion-table foo make-my-alist 'local)
+ @end example
+ @end defmac
+ 
  @node Minibuffer Completion
  @subsection Completion and the Minibuffer
  
***************
*** 1218,1223 ****
--- 1234,1248 ----
  
    Emacs uses programmed completion when completing file names.
  @xref{File Name Completion}.
+ 
+ @defmac dynamic-completion-table function
+ This macro is a convenient way to write a function that can act as
+ programmed completion function.  The argument @var{function} should be
+ a function that takes one argument, a string, and returns an alist of
+ possible completions of it.  You can think of
+ @code{dynamic-completion-table} as a transducer between that interface
+ and the interface for programmed completion functions.
+ @end defmac
  
  @node Yes-or-No Queries
  @section Yes-or-No Queries




reply via email to

[Prev in Thread] Current Thread [Next in Thread]