Minor copyedits in last manual change

* doc/emacs/custom.texi (Authentication): Improve markup,
indexing, and wording.
This commit is contained in:
Eli Zaretskii 2019-01-29 18:49:50 +02:00
parent 73508e6245
commit b94d767527

View file

@ -2614,37 +2614,37 @@ Type @kbd{C-q}, followed by the key you want to bind, to insert @var{char}.
@node Authentication @node Authentication
@section Keeping Persistent Authentication Information @section Keeping Persistent Authentication Information
@cindex ~/.authinfo file
@cindex ~/.authinfo.gpg file
@cindex ~/.netrc file
Some Emacs packages, which connect to other services, require Some Emacs packages, which connect to other services, require
authentication (@pxref{Passwords}), e.g., @ref{Top, Gnus,, gnus, The authentication (@pxref{Passwords}), e.g., see @ref{Top, Gnus,, gnus, The
Gnus Manual}, or @ref{Top, Tramp,, tramp, The Tramp Manual}. Because Gnus Manual}, or @ref{Top, Tramp,, tramp, The Tramp Manual}. Because
it might be annoying to provide the same user name and password again it might be annoying to provide the same user name and password again
and again, Emacs offers to keep this information persistent via the and again, Emacs offers to keep this information persistent via the
auth-source library. @file{auth-source} library.
Per default, this information is taken from the file @cindex @file{~/.authinfo} file
@cindex @file{~/.authinfo.gpg} file
@cindex ~/.netrc file
By default, the authentication information is taken from the file
@file{~/.authinfo} or @file{~/.authinfo.gpg} or @file{~/.netrc}. @file{~/.authinfo} or @file{~/.authinfo.gpg} or @file{~/.netrc}.
These files have a syntax similar to netrc files as known from the ftp These files have a syntax similar to netrc files as known from the
program, like @command{ftp} program, like this:
@example @example
machine @var{mymachine} login @var{myloginname} password @var{mypassword} port @var{myport} machine @var{mymachine} login @var{myloginname} password @var{mypassword} port @var{myport}
@end example @end example
Similarly, the auth-source library supports multiple storage Similarly, the @file{auth-source} library supports multiple storage
backend, currently either the classic netrc backend, JSON files, the backend, currently either the classic netrc backend, JSON files, the
Secret Service API, and pass, the standard unix password manager. Secret Service API, and pass, the standard unix password manager.
@vindex auth-sources @vindex auth-sources
All these alternatives are customized via the user option All these alternatives can be customized via the user option
@code{auth-sources}, @ref{Help for users, Emacs auth-source,, auth, @code{auth-sources}, see @ref{Help for users, Emacs auth-source,,
Emacs auth-source}. auth, Emacs auth-source}.
@vindex auth-source-save-behavior @vindex auth-source-save-behavior
When a password is entered interactively, which is not found via the When a password is entered interactively, which is not found via the
configured backend, some of the backends offer to save it configured backend, some of the backends offer to save it
persistently. This can be changed by the customizing user option persistently. This can be changed by customizing the user option
@code{auth-source-save-behavior}. @code{auth-source-save-behavior}.