mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-15 10:30:25 -08:00
Merge from emacs--devo--0
Patches applied: * emacs--devo--0 (patch 902-908) - Update from CVS - Merge from emacs--rel--22 * emacs--rel--22 (patch 131-137) - Update from CVS - Merge from gnus--rel--5.10 * gnus--rel--5.10 (patch 261-262) - Update from CVS Revision: emacs@sv.gnu.org/emacs--unicode--0--patch-278
This commit is contained in:
commit
18cd1f1a08
195 changed files with 6541 additions and 3863 deletions
26
ChangeLog
26
ChangeLog
|
|
@ -1,3 +1,7 @@
|
|||
2007-10-23 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* MAINTAINERS: Move to admin/.
|
||||
|
||||
2007-10-17 Chong Yidong <cyd@stupidchicken.com>
|
||||
|
||||
* configure.in (HAVE_RES_INIT): Define if res_init() exists.
|
||||
|
|
@ -92,7 +96,7 @@
|
|||
|
||||
* README.multi-tty: Move to admin/notes/multi-tty, with some edits.
|
||||
|
||||
2007-08-29 Karoly Lorentey <karoly@lorentey.hu>
|
||||
2007-08-29 K,Aa(Broly L$,1 q(Brentey <karoly@lorentey.hu>
|
||||
|
||||
* README.multi-tty: New file.
|
||||
|
||||
|
|
@ -163,8 +167,8 @@
|
|||
|
||||
2007-06-11 Jan Dj,Ad(Brv <jan.h.d@swipnet.se>
|
||||
|
||||
* configure.in: Change wording about yes/gtk and lucid/athena being
|
||||
synonyms.
|
||||
* configure.in: Change wording about yes/gtk and lucid/athena
|
||||
being synonyms.
|
||||
|
||||
2007-06-08 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
|
|
@ -228,8 +232,7 @@
|
|||
|
||||
2007-04-19 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* configure.in: Signal error if Xaw libs are missing in a Lucid
|
||||
build.
|
||||
* configure.in: Signal error if Xaw libs are missing in a Lucid build.
|
||||
|
||||
2007-04-18 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
|
|
@ -1976,8 +1979,7 @@
|
|||
|
||||
2000-10-01 Andreas Schwab <schwab@suse.de>
|
||||
|
||||
* Makefile.in (install-arch-indep): Update list of installed info
|
||||
files.
|
||||
* Makefile.in (install-arch-indep): Update list of installed info files.
|
||||
|
||||
2000-09-30 Gerd Moellmann <gerd@gnu.org>
|
||||
|
||||
|
|
@ -2512,7 +2514,7 @@
|
|||
|
||||
1999-02-26 Richard Stallman <rms@gnu.org>
|
||||
|
||||
* configure.in: Use epaths.h and epaths-force instead of paths....
|
||||
* configure.in: Use epaths.h and epaths-force instead of paths...
|
||||
|
||||
* Makefile.in (epaths-force): Renamed from paths-force;
|
||||
operate on epaths.in and produce epaths.h.
|
||||
|
|
@ -2663,8 +2665,7 @@
|
|||
1998-04-16 Eli Zaretskii <eliz@delysid.gnu.org>
|
||||
|
||||
* config.bat: Make sure the environment is large enough to support
|
||||
all the "set foo=bar" commands. Update pointers to DJGPP FTP
|
||||
sites.
|
||||
all the "set foo=bar" commands. Update pointers to DJGPP FTP sites.
|
||||
|
||||
1998-04-10 Karl Heuer <kwzh@gnu.org>
|
||||
|
||||
|
|
@ -2689,8 +2690,7 @@
|
|||
|
||||
1998-03-23 Kenichi Handa <handa@etl.go.jp>
|
||||
|
||||
* Makefile.in (top_distclean): Check the existence of `lock'
|
||||
subdir.
|
||||
* Makefile.in (top_distclean): Check the existence of `lock' subdir.
|
||||
|
||||
1998-03-22 Richard Stallman <rms@gnu.org>
|
||||
|
||||
|
|
@ -2866,7 +2866,7 @@
|
|||
|
||||
1997-08-22 Richard Stallman <rms@psilocin.gnu.ai.mit.edu>
|
||||
|
||||
* configure.in (HAVE_MOTIF_2_1): Test for Motif 2.1,
|
||||
* configure.in (HAVE_MOTIF_2_1): Test for Motif 2.1.
|
||||
|
||||
1997-08-22 Jonathan I. Kamens <jik@kamens.brookline.ma.us>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
2007-10-23 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* MAINTAINERS: Move here from ../.
|
||||
|
||||
2007-10-17 Juanma Barranquero <lekktu@gmail.com>
|
||||
|
||||
* make-emacs: Doc fix.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,21 @@
|
|||
2007-10-25 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* fortran-xtra.texi (Fortran): F90 mode handles F2003.
|
||||
|
||||
2007-10-24 Richard Stallman <rms@gnu.org>
|
||||
|
||||
* misc.texi (Interactive Shell): Cleanup last change.
|
||||
|
||||
2007-10-22 Juri Linkov <juri@jurta.org>
|
||||
|
||||
* mini.texi (Minibuffer History): Add text about a list of minibuffer
|
||||
default values.
|
||||
|
||||
2007-10-20 Eric S. Raymond <esr@snark.thyrsus.com>
|
||||
|
||||
* files.texi: Disambiguate two slightly different uses of the term
|
||||
'filesets'.
|
||||
|
||||
2007-10-18 Martin Rudalics <rudalics@gmx.at>
|
||||
|
||||
* trouble.texi (Quitting): Fix typo.
|
||||
|
|
|
|||
|
|
@ -1347,7 +1347,7 @@ distributed work. It differs in many ways from old well-known
|
|||
systems, such as CVS and RCS. It supports different transports for
|
||||
interoperating between users, offline operations, and it has good
|
||||
branching and merging features. It also supports atomic commits of
|
||||
fileset changes, and keeps a history of file renaming and moving. VC
|
||||
filesets, and keeps a history of file renaming and moving. VC
|
||||
does not support all operations provided by GNU Arch, so you must
|
||||
sometimes invoke it from the command line, or use a specialized
|
||||
module.
|
||||
|
|
@ -1355,7 +1355,7 @@ module.
|
|||
@cindex git
|
||||
git is a version-control system invented by Linus Torvalds to
|
||||
support Linux kernel development. Like GNU Arch, it supports atomic
|
||||
commits of fileset changes, and keeps a history of file renaming and
|
||||
commits of filesets, and keeps a history of file renaming and
|
||||
moving. One significant feature of git is that it largely abolishes
|
||||
the notion of a single centralized repository; instead, each working
|
||||
copy of a git project is its own repository and coordination is done
|
||||
|
|
@ -1638,6 +1638,11 @@ marked files, but did not pass them to the version-control backends as
|
|||
a group. Now it does, which enables VC to drive changeset-based
|
||||
version-control systems.
|
||||
|
||||
Emacs uses the concept of named filesets elsewhere
|
||||
(@pxref{Filesets}) to allow you to view and visit files in functional
|
||||
groups. Unlike those, VC filesets are not named and don't persist
|
||||
across sessions.
|
||||
|
||||
@node Doing The Right Thing
|
||||
@subsubsection Performing the next operation in the development cycle
|
||||
|
||||
|
|
@ -3061,6 +3066,11 @@ files in a fileset, and @kbd{M-x filesets-close} to close them. Use
|
|||
a fileset. These commands are also available from the @samp{Filesets}
|
||||
menu, where each existing fileset is represented by a submenu.
|
||||
|
||||
Emacs uses the concept of a fileset elsewhere @pxref{Version
|
||||
Control} to describe sets of files to be treated as a group for
|
||||
purposes of version-control operations. Those filesets are
|
||||
unnamed and do not persist across Emacs essions.
|
||||
|
||||
@ignore
|
||||
arch-tag: 768d32cb-e15a-4cc1-b7bf-62c00ee12250
|
||||
@end ignore
|
||||
|
|
|
|||
|
|
@ -32,8 +32,8 @@ command runs the hook @code{fortran-mode-hook}.
|
|||
@findex f90-mode
|
||||
@findex fortran-mode
|
||||
Fortran mode is meant for editing Fortran77 ``fixed format'' (and also
|
||||
``tab format'') source code. For editing the modern Fortran90 or
|
||||
Fortran95 ``free format'' source code, use F90 mode (@code{f90-mode}).
|
||||
``tab format'') source code. For editing the modern Fortran90/95/2003
|
||||
``free format'' source code, use F90 mode (@code{f90-mode}).
|
||||
Emacs normally uses Fortran mode for files with extension @samp{.f},
|
||||
@samp{.F} or @samp{.for}, and F90 mode for the extension @samp{.f90} and
|
||||
@samp{.f95}. GNU Fortran supports both kinds of format.
|
||||
|
|
|
|||
|
|
@ -462,10 +462,10 @@ contents of the minibuffer. To use it again unchanged, just type
|
|||
not change the history element that you ``moved'' to, but your new
|
||||
argument does go at the end of the history list in its own right.
|
||||
|
||||
For many minibuffer arguments there is a ``default'' value. You can
|
||||
insert the default value into the minibuffer as text by using
|
||||
@kbd{M-n}. You can think of this as moving ``into the future'' in the
|
||||
history.
|
||||
For many minibuffer arguments there is a ``default'' value, or
|
||||
a list of default values. You can insert the default value into the
|
||||
minibuffer as text by using @kbd{M-n} one or more times. You can
|
||||
think of this as moving ``into the future'' in the history.
|
||||
|
||||
@findex previous-matching-history-element
|
||||
@findex next-matching-history-element
|
||||
|
|
|
|||
|
|
@ -488,8 +488,8 @@ also change the coding system for a running subshell by typing
|
|||
Coding}.
|
||||
|
||||
@cindex @env{INSIDE_EMACS} environment variable
|
||||
Emacs sets the environment variable @env{INSIDE_EMACS} (to a
|
||||
comma-separated list including the Emacs version) in the subshell.
|
||||
Emacs sets the environment variable @env{INSIDE_EMACS} in the
|
||||
subshell to a comma-separated list including the Emacs version.
|
||||
Programs can check this variable to determine whether they are running
|
||||
inside an Emacs subshell.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,36 @@
|
|||
2007-10-26 Richard Stallman <rms@gnu.org>
|
||||
|
||||
* objects.texi (Equality Predicates): Null strings are uniquified.
|
||||
|
||||
* minibuf.texi: Minor clarifications in previous change.
|
||||
|
||||
2007-10-25 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* customize.texi (Variable Definitions): Add :risky and :safe keywords.
|
||||
|
||||
2007-10-24 Richard Stallman <rms@gnu.org>
|
||||
|
||||
* elisp.texi (Top): Delete Frame-Local Variables from subnode menu.
|
||||
|
||||
* variables.texi (Frame-Local Variables): Node deleted.
|
||||
(Variables): Delete Frame-Local Variables from menu.
|
||||
(Local Variables, Buffer-Local Variables, Intro to Buffer-Local)
|
||||
(Default Value): Don't mention frame-local vars.
|
||||
|
||||
* os.texi (Idle Timers): current-idle-time returns nil if not idle.
|
||||
|
||||
* loading.texi (Unloading): Document FEATURE-unload-function
|
||||
instead of FEATURE-unload-hook.
|
||||
|
||||
* frames.texi (Multiple Displays): Don't mention frame-local vars.
|
||||
|
||||
2007-10-22 Juri Linkov <juri@jurta.org>
|
||||
|
||||
* minibuf.texi (Text from Minibuffer, Minibuffer Completion)
|
||||
(High-Level Completion): Document a list of default value strings
|
||||
in the DEFAULT argument, for which minibuffer functions return the
|
||||
first element.
|
||||
|
||||
2007-10-17 Juri Linkov <juri@jurta.org>
|
||||
|
||||
* text.texi (Filling): Update arguments of fill-paragraph.
|
||||
|
|
|
|||
|
|
@ -393,6 +393,14 @@ value and then reevaluates the defcustom. By that time, the necessary
|
|||
variables and functions will be defined, so there will not be an error.
|
||||
@end table
|
||||
|
||||
@item :risky @var{value}
|
||||
@kindex risky@r{, @code{defcustom} keyword}
|
||||
Set this variable's @code{risky-local-variable} property to @var{value}.
|
||||
|
||||
@item :safe @var{function}
|
||||
@kindex safe@r{, @code{defcustom} keyword}
|
||||
Set this variable's @code{safe-local-variable} property to @var{function}.
|
||||
|
||||
@item :set-after @var{variables}
|
||||
@kindex set-after@r{, @code{defcustom} keyword}
|
||||
When setting variables according to saved customizations, make sure to
|
||||
|
|
|
|||
|
|
@ -421,7 +421,6 @@ Variables
|
|||
* Setting Variables:: Storing new values in variables.
|
||||
* Variable Scoping:: How Lisp chooses among local and global values.
|
||||
* Buffer-Local Variables:: Variable values in effect only in one buffer.
|
||||
* Frame-Local Variables:: Variable values in effect only in one frame.
|
||||
* Future Local Variables:: New kinds of local values we might add some day.
|
||||
* File Local Variables:: Handling local variable lists in files.
|
||||
* Variable Aliases:: Variables that are aliases for other variables.
|
||||
|
|
|
|||
|
|
@ -141,7 +141,7 @@ is the one for the terminal that the currently selected frame belongs
|
|||
to. These variables include @code{default-minibuffer-frame},
|
||||
@code{defining-kbd-macro}, @code{last-kbd-macro}, and
|
||||
@code{system-key-alist}. They are always terminal-local, and can never
|
||||
be buffer-local (@pxref{Buffer-Local Variables}) or frame-local.
|
||||
be buffer-local (@pxref{Buffer-Local Variables}).
|
||||
|
||||
A single X server can handle more than one screen. A display name
|
||||
@samp{@var{host}:@var{server}.@var{screen}} has three parts; the last
|
||||
|
|
|
|||
|
|
@ -1326,6 +1326,9 @@ See @ref{Autoload}.
|
|||
@item call-interactively
|
||||
See @ref{Interactive Call}.
|
||||
|
||||
@item called-interactively-p
|
||||
See @ref{Distinguish Interactive}.
|
||||
|
||||
@item commandp
|
||||
See @ref{Interactive Call}.
|
||||
|
||||
|
|
@ -1351,7 +1354,7 @@ See @ref{Function Indirection}.
|
|||
See @ref{Using Interactive}.
|
||||
|
||||
@item interactive-p
|
||||
See @ref{Interactive Call}.
|
||||
See @ref{Distinguish Interactive}.
|
||||
|
||||
@item mapatoms
|
||||
See @ref{Creating Symbols}.
|
||||
|
|
|
|||
|
|
@ -862,24 +862,27 @@ library with @code{defun}, @code{defalias}, @code{defsubst},
|
|||
It then restores any autoloads formerly associated with those symbols.
|
||||
(Loading saves these in the @code{autoload} property of the symbol.)
|
||||
|
||||
@vindex unload-feature-special-hooks
|
||||
Before restoring the previous definitions, @code{unload-feature} runs
|
||||
@code{remove-hook} to remove functions in the library from certain
|
||||
hooks. These hooks include variables whose names end in @samp{hook}
|
||||
or @samp{-hooks}, plus those listed in
|
||||
@code{unload-feature-special-hooks}. This is to prevent Emacs from
|
||||
ceasing to function because important hooks refer to functions that
|
||||
are no longer defined.
|
||||
@code{unload-feature-special-hooks}, as well as
|
||||
@code{auto-mode-alist}. This is to prevent Emacs from ceasing to
|
||||
function because important hooks refer to functions that are no longer
|
||||
defined.
|
||||
|
||||
@vindex @var{feature}-unload-hook
|
||||
Standard unloading activities also undoes ELP profiling of functions
|
||||
in that library, unprovides any features provided by the library, and
|
||||
cancels timers held in variables defined by the library.
|
||||
|
||||
@vindex @var{feature}-unload-function
|
||||
If these measures are not sufficient to prevent malfunction, a library
|
||||
can define an explicit unload hook. If @code{@var{feature}-unload-hook}
|
||||
is defined, it is run as a normal hook before restoring the previous
|
||||
definitions, @emph{instead of} the usual hook-removing actions. The
|
||||
unload hook ought to undo all the global state changes made by the
|
||||
library that might cease to work once the library is unloaded.
|
||||
@code{unload-feature} can cause problems with libraries that fail to do
|
||||
this, so it should be used with caution.
|
||||
can define an explicit unloader named @code{@var{feature}-unload-function}.
|
||||
If that symbol is defined as a function, @code{unload-feature} calls
|
||||
it with no arguments before doing anything else. It can do whatever
|
||||
is appropriate to unload the library. If it returns @code{nil},
|
||||
@code{unload-feature} proceeds to take the normal unload actions.
|
||||
Otherwise it considers the job to be done.
|
||||
|
||||
Ordinarily, @code{unload-feature} refuses to unload a library on which
|
||||
other loaded libraries depend. (A library @var{a} depends on library
|
||||
|
|
|
|||
|
|
@ -128,18 +128,19 @@ However, if @var{read} is non-@code{nil}, @code{read-from-minibuffer}
|
|||
reads the text and returns the resulting Lisp object, unevaluated.
|
||||
(@xref{Input Functions}, for information about reading.)
|
||||
|
||||
The argument @var{default} specifies a default value to make available
|
||||
through the history commands. It should be a string, or @code{nil}.
|
||||
If non-@code{nil}, the user can access it using
|
||||
@code{next-history-element}, usually bound in the minibuffer to
|
||||
@kbd{M-n}. If @var{read} is non-@code{nil}, then @var{default} is
|
||||
also used as the input to @code{read}, if the user enters empty input.
|
||||
(If @var{read} is non-@code{nil} and @var{default} is @code{nil}, empty
|
||||
The argument @var{default} specifies default values to make available
|
||||
through the history commands. It should be a string, a list of
|
||||
strings, or @code{nil}. The string or strings become the minibuffer's
|
||||
``future history,'' available to the user with @kbd{M-n}.
|
||||
|
||||
If @var{read} is non-@code{nil}, then @var{default} is also used as
|
||||
the input to @code{read}, if the user enters empty input. (If
|
||||
@var{read} is non-@code{nil} and @var{default} is @code{nil}, empty
|
||||
input results in an @code{end-of-file} error.) However, in the usual
|
||||
case (where @var{read} is @code{nil}), @code{read-from-minibuffer}
|
||||
ignores @var{default} when the user enters empty input and returns an
|
||||
empty string, @code{""}. In this respect, it is different from all
|
||||
the other minibuffer input functions in this chapter.
|
||||
empty string, @code{""}. In this respect, it differs from all the
|
||||
other minibuffer input functions in this chapter.
|
||||
|
||||
If @var{keymap} is non-@code{nil}, that keymap is the local keymap to
|
||||
use in the minibuffer. If @var{keymap} is omitted or @code{nil}, the
|
||||
|
|
@ -176,10 +177,14 @@ The keymap used is @code{minibuffer-local-map}.
|
|||
The optional argument @var{default} is used as in
|
||||
@code{read-from-minibuffer}, except that, if non-@code{nil}, it also
|
||||
specifies a default value to return if the user enters null input. As
|
||||
in @code{read-from-minibuffer} it should be a string, or @code{nil},
|
||||
which is equivalent to an empty string.
|
||||
in @code{read-from-minibuffer} it should be a string, a list of
|
||||
strings, or @code{nil} which is equivalent to an empty string. When
|
||||
@var{default} is a string, that string is the default value. When it
|
||||
is a list of strings, the first string is the default value. (All
|
||||
these strings are available to the user in the ``future minibuffer
|
||||
history.'')
|
||||
|
||||
This function is a simplified interface to the
|
||||
This function works by calling the
|
||||
@code{read-from-minibuffer} function:
|
||||
|
||||
@smallexample
|
||||
|
|
@ -190,7 +195,7 @@ This function is a simplified interface to the
|
|||
(read-from-minibuffer @var{prompt} @var{initial} nil nil
|
||||
@var{history} @var{default} @var{inherit})))
|
||||
(if (and (equal value "") @var{default})
|
||||
@var{default}
|
||||
(if (consp @var{default}) (car @var{default}) @var{default})
|
||||
value))
|
||||
@end group
|
||||
@end smallexample
|
||||
|
|
@ -839,10 +844,11 @@ an element of @var{collection}. If @var{require-match} is neither
|
|||
input already in the buffer matches an element of @var{collection}.
|
||||
|
||||
However, empty input is always permitted, regardless of the value of
|
||||
@var{require-match}; in that case, @code{completing-read} returns
|
||||
@var{default}, or @code{""}, if @var{default} is @code{nil}. The
|
||||
value of @var{default} (if non-@code{nil}) is also available to the
|
||||
user through the history commands.
|
||||
@var{require-match}; in that case, @code{completing-read} returns the
|
||||
first element of @var{default}, if it is a list; @code{""}, if
|
||||
@var{default} is @code{nil}; or @var{default}. The string or strins
|
||||
in @var{default} aer also available to the user through the history
|
||||
commands.
|
||||
|
||||
The function @code{completing-read} uses
|
||||
@code{minibuffer-local-completion-map} as the keymap if
|
||||
|
|
@ -1073,8 +1079,10 @@ specification. @xref{Defining Commands}.
|
|||
This function reads the name of a buffer and returns it as a string.
|
||||
The argument @var{default} is the default name to use, the value to
|
||||
return if the user exits with an empty minibuffer. If non-@code{nil},
|
||||
it should be a string or a buffer. It is mentioned in the prompt, but
|
||||
is not inserted in the minibuffer as initial input.
|
||||
it should be a string, a list of strings, or a buffer. If it is
|
||||
a list, the default value is the first element of this list. It is
|
||||
mentioned in the prompt, but is not inserted in the minibuffer as
|
||||
initial input.
|
||||
|
||||
The argument @var{prompt} should be a string ending with a colon and a
|
||||
space. If @var{default} is non-@code{nil}, the function inserts it in
|
||||
|
|
@ -1130,11 +1138,12 @@ which @code{commandp} returns @code{t}, and a command name is a symbol
|
|||
for which @code{commandp} returns @code{t}. @xref{Interactive Call}.
|
||||
|
||||
The argument @var{default} specifies what to return if the user enters
|
||||
null input. It can be a symbol or a string; if it is a string,
|
||||
@code{read-command} interns it before returning it. If @var{default} is
|
||||
@code{nil}, that means no default has been specified; then if the user
|
||||
enters null input, the return value is @code{(intern "")}, that is, a
|
||||
symbol whose name is an empty string.
|
||||
null input. It can be a symbol, a string or a list of strings. If it
|
||||
is a string, @code{read-command} interns it before returning it.
|
||||
If it is a list, @code{read-command} returns the first element of this list.
|
||||
If @var{default} is @code{nil}, that means no default has been
|
||||
specified; then if the user enters null input, the return value is
|
||||
@code{(intern "")}, that is, a symbol whose name is an empty string.
|
||||
|
||||
@example
|
||||
(read-command "Command name? ")
|
||||
|
|
@ -1176,11 +1185,13 @@ complete in the set of extant Lisp symbols, and it uses the
|
|||
This function reads the name of a user variable and returns it as a
|
||||
symbol.
|
||||
|
||||
The argument @var{default} specifies what to return if the user enters
|
||||
null input. It can be a symbol or a string; if it is a string,
|
||||
@code{read-variable} interns it before returning it. If @var{default}
|
||||
is @code{nil}, that means no default has been specified; then if the
|
||||
user enters null input, the return value is @code{(intern "")}.
|
||||
The argument @var{default} specifies the default value to return if
|
||||
the user enters null input. It can be a symbol, a string, or a list
|
||||
of strings. If it is a string, @code{read-variable} interns it to
|
||||
make the default value; If it is a list, @code{read-variable} interns
|
||||
the first element. If @var{default} is @code{nil}, that means no
|
||||
default has been specified; then if the user enters null input, the
|
||||
return value is @code{(intern "")}.
|
||||
|
||||
@example
|
||||
@group
|
||||
|
|
|
|||
|
|
@ -1871,7 +1871,7 @@ This function returns a symbol naming the primitive type of
|
|||
@cindex equality
|
||||
|
||||
Here we describe two functions that test for equality between any two
|
||||
objects. Other functions test equality between objects of specific
|
||||
objects. Other functions test equality of contents between objects of specific
|
||||
types, e.g., strings. For these predicates, see the appropriate chapter
|
||||
describing the data type.
|
||||
|
||||
|
|
@ -1904,6 +1904,13 @@ by the same change in the contents of the other.
|
|||
@result{} nil
|
||||
@end group
|
||||
|
||||
@group
|
||||
(eq "" "")
|
||||
@result{} t
|
||||
;; @r{This exception occurs because Emacs Lisp}
|
||||
;; @r{makes just one multibyte empty string, to save space.}
|
||||
@end group
|
||||
|
||||
@group
|
||||
(eq '(1 (2 (3))) '(1 (2 (3))))
|
||||
@result{} nil
|
||||
|
|
|
|||
|
|
@ -1561,10 +1561,10 @@ set up to repeat will subsequently run another time, one by one.
|
|||
|
||||
@c Emacs 19 feature
|
||||
@defun current-idle-time
|
||||
This function returns the length of time Emacs has been idle, as a
|
||||
list of three integers: @code{(@var{high} @var{low} @var{microsec})}.
|
||||
The integers @var{high} and @var{low} combine to give the number of
|
||||
seconds of idleness, which is
|
||||
If Emacs is idle, this function returns the length of time Emacs has
|
||||
been idle, as a list of three integers: @code{(@var{high} @var{low}
|
||||
@var{microsec})}. The integers @var{high} and @var{low} combine to
|
||||
give the number of seconds of idleness, which is
|
||||
@ifnottex
|
||||
@var{high} * 2**16 + @var{low}.
|
||||
@end ifnottex
|
||||
|
|
@ -1576,6 +1576,9 @@ The third element, @var{microsec}, gives the microseconds since the
|
|||
start of the current second (or 0 for systems that return time with
|
||||
the resolution of only one second).
|
||||
|
||||
When Emacs is not idle, @code{current-idle-time} returns @code{nil}.
|
||||
This is a convenient way to test whether Emacs is idle.
|
||||
|
||||
The main use of this function is when an idle timer function wants to
|
||||
``take a break'' for a while. It can set up another idle timer to
|
||||
call the same function again, after a few seconds more idleness.
|
||||
|
|
|
|||
|
|
@ -39,7 +39,6 @@ variable.
|
|||
* Setting Variables:: Storing new values in variables.
|
||||
* Variable Scoping:: How Lisp chooses among local and global values.
|
||||
* Buffer-Local Variables:: Variable values in effect only in one buffer.
|
||||
* Frame-Local Variables:: Variable values in effect only in one frame.
|
||||
* Future Local Variables:: New kinds of local values we might add some day.
|
||||
* File Local Variables:: Handling local variable lists in files.
|
||||
* Variable Aliases:: Variables that are aliases for other variables.
|
||||
|
|
@ -255,11 +254,10 @@ Macro calls (@pxref{Macros}).
|
|||
@end itemize
|
||||
|
||||
Variables can also have buffer-local bindings (@pxref{Buffer-Local
|
||||
Variables}) and frame-local bindings (@pxref{Frame-Local Variables}); a
|
||||
few variables have terminal-local bindings (@pxref{Multiple Displays}).
|
||||
These kinds of bindings work somewhat like ordinary local bindings, but
|
||||
they are localized depending on ``where'' you are in Emacs, rather than
|
||||
localized in time.
|
||||
Variables}); a few variables have terminal-local bindings
|
||||
(@pxref{Multiple Displays}). These kinds of bindings work somewhat
|
||||
like ordinary local bindings, but they are localized depending on
|
||||
``where'' you are in Emacs, rather than localized in time.
|
||||
|
||||
@defvar max-specpdl-size
|
||||
@anchor{Definition of max-specpdl-size}
|
||||
|
|
@ -1085,16 +1083,12 @@ use short names like @code{x}.
|
|||
@cindex buffer-local variables
|
||||
|
||||
Global and local variable bindings are found in most programming
|
||||
languages in one form or another. Emacs, however, also supports additional,
|
||||
unusual kinds of variable binding: @dfn{buffer-local} bindings, which
|
||||
apply only in one buffer, and @dfn{frame-local} bindings, which apply only in
|
||||
one frame. Having different values for a variable in different buffers
|
||||
and/or frames is an important customization method.
|
||||
|
||||
This section describes buffer-local bindings; for frame-local
|
||||
bindings, see the following section, @ref{Frame-Local Variables}. (A few
|
||||
variables have bindings that are local to each terminal; see
|
||||
@ref{Multiple Displays}.)
|
||||
languages in one form or another. Emacs, however, also supports
|
||||
additional, unusual kinds of variable binding, such as
|
||||
@dfn{buffer-local} bindings, which apply only in one buffer. Having
|
||||
different values for a variable in different buffers is an important
|
||||
customization method. (A few variables have bindings that are local
|
||||
to each terminal; see @ref{Multiple Displays}.)
|
||||
|
||||
@menu
|
||||
* Intro to Buffer-Local:: Introduction and concepts.
|
||||
|
|
@ -1121,8 +1115,7 @@ this is the global binding.
|
|||
other buffers. The default binding is shared by all the buffers that
|
||||
don't have their own bindings for the variable. (This includes all
|
||||
newly-created buffers.) If you set the variable in a buffer that does
|
||||
not have a buffer-local binding for it, this sets the default binding
|
||||
(assuming there are no frame-local bindings to complicate the matter),
|
||||
not have a buffer-local binding for it, this sets the default binding,
|
||||
so the new value is visible in all the buffers that see the default
|
||||
binding.
|
||||
|
||||
|
|
@ -1153,11 +1146,11 @@ the default binding untouched. This means that the default value cannot
|
|||
be changed with @code{setq} in any buffer; the only way to change it is
|
||||
with @code{setq-default}.
|
||||
|
||||
@strong{Warning:} When a variable has buffer-local or frame-local
|
||||
@strong{Warning:} When a variable has buffer-local
|
||||
bindings in one or more buffers, @code{let} rebinds the binding that's
|
||||
currently in effect. For instance, if the current buffer has a
|
||||
buffer-local value, @code{let} temporarily rebinds that. If no
|
||||
buffer-local or frame-local bindings are in effect, @code{let} rebinds
|
||||
buffer-local bindings are in effect, @code{let} rebinds
|
||||
the default value. If inside the @code{let} you then change to a
|
||||
different current buffer in which a different binding is in effect,
|
||||
you won't see the @code{let} binding any more. And if you exit the
|
||||
|
|
@ -1421,7 +1414,7 @@ this variable.
|
|||
@c Emacs 19 feature
|
||||
The special forms @code{defvar} and @code{defconst} also set the
|
||||
default value (if they set the variable at all), rather than any
|
||||
buffer-local or frame-local value.
|
||||
buffer-local value.
|
||||
|
||||
@defun default-value symbol
|
||||
This function returns @var{symbol}'s default value. This is the value
|
||||
|
|
@ -1520,112 +1513,6 @@ an ordinary evaluated argument.
|
|||
@end example
|
||||
@end defun
|
||||
|
||||
@node Frame-Local Variables
|
||||
@section Frame-Local Variables
|
||||
@cindex frame-local variables
|
||||
|
||||
Just as variables can have buffer-local bindings, they can also have
|
||||
frame-local bindings. These bindings belong to one frame, and are in
|
||||
effect when that frame is selected. Frame-local bindings are actually
|
||||
frame parameters: you create a frame-local binding in a specific frame
|
||||
by calling @code{modify-frame-parameters} and specifying the variable
|
||||
name as the parameter name.
|
||||
|
||||
To enable frame-local bindings for a certain variable, call the function
|
||||
@code{make-variable-frame-local}.
|
||||
|
||||
@deffn Command make-variable-frame-local variable
|
||||
Enable the use of frame-local bindings for @var{variable}. This does
|
||||
not in itself create any frame-local bindings for the variable; however,
|
||||
if some frame already has a value for @var{variable} as a frame
|
||||
parameter, that value automatically becomes a frame-local binding.
|
||||
|
||||
If @var{variable} does not have a default value, then calling this
|
||||
command will give it a default value of @code{nil}. If @var{variable}
|
||||
already has a default value, that value remains unchanged.
|
||||
|
||||
If the variable is terminal-local, this function signals an error,
|
||||
because such variables cannot have frame-local bindings as well.
|
||||
@xref{Multiple Displays}. A few variables that are implemented
|
||||
specially in Emacs can be buffer-local, but can never be frame-local.
|
||||
|
||||
This command returns @var{variable}.
|
||||
@end deffn
|
||||
|
||||
Buffer-local bindings take precedence over frame-local bindings. Thus,
|
||||
consider a variable @code{foo}: if the current buffer has a buffer-local
|
||||
binding for @code{foo}, that binding is active; otherwise, if the
|
||||
selected frame has a frame-local binding for @code{foo}, that binding is
|
||||
active; otherwise, the default binding of @code{foo} is active.
|
||||
|
||||
Here is an example. First we prepare a few bindings for @code{foo}:
|
||||
|
||||
@example
|
||||
(setq f1 (selected-frame))
|
||||
(make-variable-frame-local 'foo)
|
||||
|
||||
;; @r{Make a buffer-local binding for @code{foo} in @samp{b1}.}
|
||||
(set-buffer (get-buffer-create "b1"))
|
||||
(make-local-variable 'foo)
|
||||
(setq foo '(b 1))
|
||||
|
||||
;; @r{Make a frame-local binding for @code{foo} in a new frame.}
|
||||
;; @r{Store that frame in @code{f2}.}
|
||||
(setq f2 (make-frame))
|
||||
(modify-frame-parameters f2 '((foo . (f 2))))
|
||||
@end example
|
||||
|
||||
Now we examine @code{foo} in various contexts. Whenever the
|
||||
buffer @samp{b1} is current, its buffer-local binding is in effect,
|
||||
regardless of the selected frame:
|
||||
|
||||
@example
|
||||
(select-frame f1)
|
||||
(set-buffer (get-buffer-create "b1"))
|
||||
foo
|
||||
@result{} (b 1)
|
||||
|
||||
(select-frame f2)
|
||||
(set-buffer (get-buffer-create "b1"))
|
||||
foo
|
||||
@result{} (b 1)
|
||||
@end example
|
||||
|
||||
@noindent
|
||||
Otherwise, the frame gets a chance to provide the binding; when frame
|
||||
@code{f2} is selected, its frame-local binding is in effect:
|
||||
|
||||
@example
|
||||
(select-frame f2)
|
||||
(set-buffer (get-buffer "*scratch*"))
|
||||
foo
|
||||
@result{} (f 2)
|
||||
@end example
|
||||
|
||||
@noindent
|
||||
When neither the current buffer nor the selected frame provides
|
||||
a binding, the default binding is used:
|
||||
|
||||
@example
|
||||
(select-frame f1)
|
||||
(set-buffer (get-buffer "*scratch*"))
|
||||
foo
|
||||
@result{} nil
|
||||
@end example
|
||||
|
||||
@noindent
|
||||
When the active binding of a variable is a frame-local binding, setting
|
||||
the variable changes that binding. You can observe the result with
|
||||
@code{frame-parameters}:
|
||||
|
||||
@example
|
||||
(select-frame f2)
|
||||
(set-buffer (get-buffer "*scratch*"))
|
||||
(setq foo 'nobody)
|
||||
(assq 'foo (frame-parameters f2))
|
||||
@result{} (foo . nobody)
|
||||
@end example
|
||||
|
||||
@node Future Local Variables
|
||||
@section Possible Future Local Variables
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,46 @@
|
|||
2007-10-25 Jonathan Yavner <jyavner@member.fsf.org>
|
||||
|
||||
* ses.texi (The Basics): Mention how to create a new spreadsheet.
|
||||
Mention the new three-letter column identifiers.
|
||||
(More on cell printing): Calculate-cell and truncate-cell are now `c'
|
||||
and `t' rather than `C-c C-c' and `C-c C-t'. Mention the stupid error
|
||||
message when using `c' on an empty default with default printer.
|
||||
(Buffer-local variables in spreadsheets): `symbolic-formulas' was
|
||||
renamed to `ses--symbolic-formulas' some time ago.
|
||||
|
||||
2007-10-25 Jay Belanger <jay.p.belanger@gmail.com>
|
||||
|
||||
* calc.texi (Default Simplifications, Making Selections)
|
||||
(Customizing Calc): Clarify associativity of multiplication.
|
||||
|
||||
2007-10-23 Michael Albinus <michael.albinus@gmx.de>
|
||||
|
||||
* tramp.texi (Traces and Profiles): Simplify loop over
|
||||
`trace-function-background'.
|
||||
|
||||
2007-10-22 Juri Linkov <juri@jurta.org>
|
||||
|
||||
* dired-x.texi (Shell Command Guessing): Default values are now
|
||||
available by typing M-n instead of M-p.
|
||||
|
||||
2007-10-21 Michael Albinus <michael.albinus@gmx.de>
|
||||
|
||||
* tramp.texi (Cleanup remote connections): New section.
|
||||
(Password caching): Remove `tramp-clear-passwd'.
|
||||
It's not a command anymore.
|
||||
(Bug Reports): Add `tramp-bug' to function index.
|
||||
(Function Index, Variable Index): New nodes.
|
||||
(Remote shell setup): Describe `tramp-password-prompt-regexp'.
|
||||
|
||||
* trampver.texi: Update release number.
|
||||
|
||||
2007-10-20 Jay Belanger <jay.p.belanger@gmail.com>
|
||||
|
||||
* calc.texi (History and Acknowledgements): Turn comment
|
||||
about integer size into past tense.
|
||||
(Time Zones): Remove pointer to Calc author's address.
|
||||
(Trigonometric and Hyperbolic Functions): Mention cotangent
|
||||
and hyperbolic cotangent.
|
||||
and hyperbolic cotangent. Fix typo.
|
||||
|
||||
2007-10-10 Michael Albinus <michael.albinus@gmx.de>
|
||||
|
||||
|
|
@ -56,13 +92,12 @@
|
|||
|
||||
2007-09-08 Michael Olson <mwolson@gnu.org>
|
||||
|
||||
* erc.texi (Copying): New section included from gpl.texi. This matches
|
||||
the look of the upstream ERC manual.
|
||||
* erc.texi (Copying): New section included from gpl.texi.
|
||||
This matches the look of the upstream ERC manual.
|
||||
|
||||
2007-09-07 Jay Belanger <jay.p.belanger@gmail.com>
|
||||
|
||||
* calc.texi (History and Acknowledgements): Adjust the
|
||||
"thanks".
|
||||
* calc.texi (History and Acknowledgements): Adjust the "thanks".
|
||||
(Random Numbers): Clarify the distribution of `random'.
|
||||
|
||||
2007-09-06 Glenn Morris <rgm@gnu.org>
|
||||
|
|
@ -98,7 +133,7 @@
|
|||
|
||||
2007-08-30 Carsten Dominik <dominik@science.uva.nl>
|
||||
|
||||
* org.texi: Version 5.07
|
||||
* org.texi: Version 5.07.
|
||||
|
||||
2007-08-24 IRIE Tetsuya <irie@t.email.ne.jp> (tiny change)
|
||||
|
||||
|
|
|
|||
|
|
@ -18324,7 +18324,7 @@ The remaining trigonometric functions, @code{calc-sec} [@code{sec}],
|
|||
available. With the Hyperbolic flag, these compute their hyperbolic
|
||||
counterparts, which are also available separately as @code{calc-sech}
|
||||
[@code{sech}], @code{calc-csch} [@code{csch}] and @code{calc-coth}
|
||||
[@code{coth}]. (These commmands do not accept the Inverse flag.)
|
||||
[@code{coth}]. (These commands do not accept the Inverse flag.)
|
||||
|
||||
@node Advanced Math Functions, Branch Cuts, Trigonometric and Hyperbolic Functions, Scientific Functions
|
||||
@section Advanced Mathematical Functions
|
||||
|
|
@ -21357,16 +21357,17 @@ entire four-term sum.
|
|||
@pindex calc-break-selections
|
||||
The @kbd{j b} (@code{calc-break-selections}) command controls a mode
|
||||
in which the ``deep structure'' of these associative formulas shows
|
||||
through. Calc actually stores the above formulas as @samp{((a + b) - c) + d}
|
||||
and @samp{x * (y * z)}. (Note that for certain obscure reasons, Calc
|
||||
treats multiplication as right-associative.) Once you have enabled
|
||||
@kbd{j b} mode, selecting with the cursor on the @samp{-} sign would
|
||||
only select the @samp{a + b - c} portion, which makes sense when the
|
||||
deep structure of the sum is considered. There is no way to select
|
||||
the @samp{b - c + d} portion; although this might initially look
|
||||
like just as legitimate a sub-formula as @samp{a + b - c}, the deep
|
||||
structure shows that it isn't. The @kbd{d U} command can be used
|
||||
to view the deep structure of any formula (@pxref{Normal Language Modes}).
|
||||
through. Calc actually stores the above formulas as
|
||||
@samp{((a + b) - c) + d} and @samp{x * (y * z)}. (Note that for certain
|
||||
obscure reasons, by default Calc treats multiplication as
|
||||
right-associative.) Once you have enabled @kbd{j b} mode, selecting
|
||||
with the cursor on the @samp{-} sign would only select the @samp{a + b -
|
||||
c} portion, which makes sense when the deep structure of the sum is
|
||||
considered. There is no way to select the @samp{b - c + d} portion;
|
||||
although this might initially look like just as legitimate a sub-formula
|
||||
as @samp{a + b - c}, the deep structure shows that it isn't. The @kbd{d
|
||||
U} command can be used to view the deep structure of any formula
|
||||
(@pxref{Normal Language Modes}).
|
||||
|
||||
When @kbd{j b} mode has not been enabled, the deep structure is
|
||||
generally hidden by the selection commands---what you see is what
|
||||
|
|
@ -22158,13 +22159,13 @@ Arithmetic operators like @kbd{+} and @kbd{*} always take two
|
|||
arguments in Calc's internal form. Sums and products of three or
|
||||
more terms are arranged by the associative law of algebra into
|
||||
a left-associative form for sums, @expr{((a + b) + c) + d}, and
|
||||
a right-associative form for products, @expr{a * (b * (c * d))}.
|
||||
Formulas like @expr{(a + b) + (c + d)} are rearranged to
|
||||
left-associative form, though this rarely matters since Calc's
|
||||
algebra commands are designed to hide the inner structure of
|
||||
sums and products as much as possible. Sums and products in
|
||||
their proper associative form will be written without parentheses
|
||||
in the examples below.
|
||||
(by default) a right-associative form for products,
|
||||
@expr{a * (b * (c * d))}. Formulas like @expr{(a + b) + (c + d)} are
|
||||
rearranged to left-associative form, though this rarely matters since
|
||||
Calc's algebra commands are designed to hide the inner structure of sums
|
||||
and products as much as possible. Sums and products in their proper
|
||||
associative form will be written without parentheses in the examples
|
||||
below.
|
||||
|
||||
Sums and products are @emph{not} rearranged according to the
|
||||
commutative law (@expr{a + b} to @expr{b + a}) except in a few
|
||||
|
|
@ -34868,12 +34869,14 @@ and @code{calc-embedded-open-close-plain-alist}.
|
|||
|
||||
@defvar calc-multiplication-has-precedence
|
||||
The variable @code{calc-multiplication-has-precedence} determines
|
||||
whether multiplication has precedence over division in algebraic formulas
|
||||
in normal language modes. If @code{calc-multiplication-has-precedence}
|
||||
is non-@code{nil}, then multiplication has precedence, and so for
|
||||
example @samp{a/b*c} will be interpreted as @samp{a/(b*c)}. If
|
||||
@code{calc-multiplication-has-precedence} is @code{nil}, then
|
||||
multiplication has the same precedence as division, and so for example
|
||||
whether multiplication has precedence over division in algebraic
|
||||
formulas in normal language modes. If
|
||||
@code{calc-multiplication-has-precedence} is non-@code{nil}, then
|
||||
multiplication has precedence (and, for certain obscure reasons, is
|
||||
right associative), and so for example @samp{a/b*c} will be interpreted
|
||||
as @samp{a/(b*c)}. If @code{calc-multiplication-has-precedence} is
|
||||
@code{nil}, then multiplication has the same precedence as division
|
||||
(and, like division, is left associative), and so for example
|
||||
@samp{a/b*c} will be interpreted as @samp{(a/b)*c}. The default value
|
||||
of @code{calc-multiplication-has-precedence} is @code{t}.
|
||||
@end defvar
|
||||
|
|
|
|||
|
|
@ -656,11 +656,11 @@ on a file named @file{foo.tar} and you press @kbd{!}, Dired will guess
|
|||
you want to @samp{tar xvf} it and suggest that as the default shell
|
||||
command.
|
||||
|
||||
The default is mentioned in brackets and you can type @kbd{M-p} to get
|
||||
The default is mentioned in brackets and you can type @kbd{M-n} to get
|
||||
the default into the minibuffer and then edit it, e.g., to change
|
||||
@samp{tar xvf} to @samp{tar tvf}. If there are several commands for a given
|
||||
file, e.g., @samp{xtex} and @samp{dvips} for a @file{.dvi} file, you can type
|
||||
@kbd{M-p} several times to see each of the matching commands.
|
||||
@kbd{M-n} several times to see each of the matching commands.
|
||||
|
||||
Dired only tries to guess a command for a single file, never for a list
|
||||
of marked files.
|
||||
|
|
|
|||
|
|
@ -115,10 +115,14 @@ To report bugs, send email to @email{jyavner@@member.fsf.org}.
|
|||
@findex set-mark-command
|
||||
@findex keyboard-quit
|
||||
|
||||
To create a new spreadsheet, visit a nonexistent file whose name ends
|
||||
with ".ses". For example, @kbd{C-x C-f test.ses RET}.
|
||||
|
||||
|
||||
A @dfn{cell identifier} is a symbol with a column letter and a row
|
||||
number. Cell B7 is the 2nd column of the 7th row. For very wide
|
||||
spreadsheets, there are two column letters: cell AB7 is the 28th
|
||||
column of the 7th row.
|
||||
column of the 7th row. Super wide spreadsheets get AAA1, etc.
|
||||
|
||||
@table @kbd
|
||||
@item j
|
||||
|
|
@ -658,21 +662,26 @@ SES could get confused by printer results that contain newlines or
|
|||
tabs, so these are replaced with question marks.
|
||||
|
||||
@table @kbd
|
||||
@item C-c C-t
|
||||
@item t
|
||||
Confine a cell to its own column (@code{ses-truncate-cell}). This
|
||||
allows you to move point to a rightward cell that would otherwise be
|
||||
covered by a spill-over. If you don't change the rightward cell, the
|
||||
confined cell will spill over again the next time it is reprinted.
|
||||
|
||||
@item C-c C-c
|
||||
When applied to a single cell, this command displays in the echo area any
|
||||
formula error or printer error that occurred during
|
||||
recalculation/reprinting (@code{ses-recalculate-cell}).
|
||||
@item c
|
||||
When applied to a single cell, this command displays in the echo area
|
||||
any formula error or printer error that occurred during
|
||||
recalculation/reprinting (@code{ses-recalculate-cell}). You can use
|
||||
this to undo the effect of @kbd{t}.
|
||||
@end table
|
||||
|
||||
When a printer function signals an error, the default printer
|
||||
When a printer function signals an error, the fallback printer
|
||||
@samp{"%s"} is substituted. This is useful when your column printer
|
||||
is numeric-only and you use a string as a cell value.
|
||||
is numeric-only and you use a string as a cell value. Note that the
|
||||
standard default printer is ``%.7g'' which is numeric-only, so cells
|
||||
that are empty of contain strings will use the fallback printer.
|
||||
@kbd{c} on such cells will display ``Format specifier doesn't match
|
||||
argument type''.
|
||||
|
||||
|
||||
@node Import and export, Virus protection, More on cell printing, Advanced Features
|
||||
|
|
@ -871,12 +880,12 @@ You can add additional local variables to the list at the bottom of
|
|||
the data area, such as hidden constants you want to refer to in your
|
||||
formulas.
|
||||
|
||||
You can override the variable @code{symbolic-formulas} to be a list of
|
||||
You can override the variable @code{ses--symbolic-formulas} to be a list of
|
||||
symbols (as parenthesized strings) to show as completions for the '
|
||||
command. This initial completions list is used instead of the actual
|
||||
set of symbols-as-formulas in the spreadsheet.
|
||||
|
||||
For examples of these, see file @file{etc/ses-example.ses}.
|
||||
For an example of this, see file @file{etc/ses-example.ses}.
|
||||
|
||||
If (for some reason) you want your formulas or printers to save data
|
||||
into variables, you must declare these variables as buffer-locals in
|
||||
|
|
|
|||
|
|
@ -164,6 +164,8 @@ For the end user:
|
|||
* Usage:: An overview of the operation of @value{tramp}.
|
||||
* Bug Reports:: Reporting Bugs and Problems.
|
||||
* Frequently Asked Questions:: Questions and answers from the mailing list.
|
||||
* Function Index:: @value{tramp} functions.
|
||||
* Variable Index:: User options and variables.
|
||||
* Concept Index:: An item for each concept.
|
||||
|
||||
For the developer:
|
||||
|
|
@ -214,6 +216,7 @@ Using @value{tramp}
|
|||
* Alternative Syntax:: URL-like filename syntax.
|
||||
* Filename completion:: Filename completion.
|
||||
* Remote processes:: Integration with other @value{emacsname} packages.
|
||||
* Cleanup remote connections:: Cleanup remote connections.
|
||||
|
||||
The inner workings of remote version control
|
||||
|
||||
|
|
@ -1548,12 +1551,6 @@ variable @code{password-cache-expiry}. The value is the number of
|
|||
seconds how long passwords are cached. Setting it to @code{nil}
|
||||
disables the expiration.
|
||||
|
||||
@findex tramp-clear-passwd
|
||||
A password is removed from the cache if a connection isn't established
|
||||
successfully. You can remove a password from the cache also by
|
||||
executing @kbd{M-x tramp-clear-passwd} in a buffer containing a
|
||||
related remote file or directory.
|
||||
|
||||
@vindex password-cache
|
||||
If you don't like this feature for security reasons, password caching
|
||||
can be disabled totally by customizing the variable
|
||||
|
|
@ -1654,7 +1651,6 @@ you must exit @value{emacsname}, remove your persistency file
|
|||
|
||||
|
||||
@node Remote shell setup
|
||||
@comment node-name, next, previous, up
|
||||
@section Remote shell setup hints
|
||||
@cindex remote shell setup
|
||||
@cindex @file{.profile} file
|
||||
|
|
@ -1719,6 +1715,39 @@ different user. The default value of
|
|||
@code{shell-prompt-pattern}, which is reported to work well in many
|
||||
circumstances.
|
||||
|
||||
@item @var{tramp-password-prompt-regexp}
|
||||
@vindex tramp-password-prompt-regexp
|
||||
@vindex tramp-wrong-passwd-regexp
|
||||
|
||||
During login, @value{tramp} might be forced to enter a password or a
|
||||
passphrase. The difference between both is that a password is
|
||||
requested from the shell on the remote host, while a passphrase is
|
||||
needed for accessing local authentication information, like your ssh
|
||||
key.
|
||||
|
||||
@var{tramp-password-prompt-regexp} handles the detection of such
|
||||
requests for English environments. When you use another localization
|
||||
of your (local or remote) host, you might need to adapt this. Example:
|
||||
|
||||
@lisp
|
||||
(setq
|
||||
tramp-password-prompt-regexp
|
||||
(concat
|
||||
"^.*"
|
||||
(regexp-opt
|
||||
'("passphrase" "Passphrase"
|
||||
;; English
|
||||
"password" "Password"
|
||||
;; Deutsch
|
||||
"passwort" "Passwort"
|
||||
;; Fran@,{c}ais
|
||||
"mot de passe" "Mot de passe") t)
|
||||
".*: | ||||