@noindent
Type @kbd{C-q}, followed by the key you want to bind, to insert @var{char}.
+@node Early Init File
+@subsection The Early Init File
+@cindex early init file
+
+ Most customizations for Emacs should be put in the normal init file,
+@file{.emacs} or @file{~/.emacs.d/init.el}. However, it is sometimes desirable
+to have customizations that take effect during Emacs startup earlier than the
+normal init file is processed. Such customizations can be put in the early
+init file, @file{~/.emacs.d/early-init.el}. This file is loaded before the
+package system and GUI is initialized, so in it you can customize variables
+that affect frame appearance as well as the package initialization process,
+such as @code{package-enable-at-startup}, @code{package-load-list}, and
+@code{package-user-dir}. Note that variables like @code{package-archives}
+which only affect the installation of new packages, and not the process of
+making already-installed packages available, may be customized in the regular
+init file. @xref{Package Installation}.
+
+ We do not recommend that you move into @file{early-init.el}
+customizations that can be left in the normal init files. That is
+because the early init file is read before the GUI is initialized, so
+customizations related to GUI features will not work reliably in
+@file{early-init.el}. By contrast, the normal init files are read
+after the GUI is initialized. If you must have customizations in the
+early init file that rely on GUI features, make them run off hooks
+provided by the Emacs startup, such as @code{window-setup-hook} or
+@code{tty-setup-hook}. @xref{Hooks}.
+
+ For more information on the early init file, @pxref{Init File,,,
+elisp, The Emacs Lisp Reference Manual}.
++
+ @node Authentication
+ @section Keeping Persistent Authentication Information
+
+ Some Emacs packages, which connect to other services, require
+ authentication (@pxref{Passwords}), e.g., see @ref{Top, Gnus,, gnus, The
+ Gnus Manual}, or @ref{Top, Tramp,, tramp, The Tramp Manual}. Because
+ it might be annoying to provide the same user name and password again
+ and again, Emacs offers to keep this information persistent via the
+ @file{auth-source} library.
+
+ @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}.
+ These files have a syntax similar to netrc files as known from the
+ @command{ftp} program, like this:
+
+ @example
+ machine @var{mymachine} login @var{myloginname} password @var{mypassword} port @var{myport}
+ @end example
+
+ Similarly, the @file{auth-source} library supports multiple storage
+ backend, currently either the classic netrc backend, JSON files, the
+ Secret Service API, and pass, the standard unix password manager.
+
+ @vindex auth-sources
+ All these alternatives can be customized via the user option
+ @code{auth-sources}, see @ref{Help for users, Emacs auth-source,,
+ auth, Emacs auth-source}.
+
+ @vindex auth-source-save-behavior
+ When a password is entered interactively, which is not found via the
+ configured backend, some of the backends offer to save it
+ persistently. This can be changed by customizing the user option
+ @code{auth-source-save-behavior}.
(edges (and (null image-transform-resize)
(window-inside-pixel-edges
(get-buffer-window (current-buffer)))))
- (type (if (fboundp 'imagemagick-types)
+ (type (if (image--imagemagick-wanted-p filename)
'imagemagick
(image-type file-or-data nil data-p)))
+ ;; :scale 1: If we do not set this, create-image will apply
+ ;; default scaling based on font size.
(image (if (not edges)
- (create-image file-or-data type data-p)
- (create-image file-or-data type data-p
+ (create-image file-or-data type data-p :scale 1)
+ (create-image file-or-data type data-p :scale 1
:max-width (- (nth 2 edges) (nth 0 edges))
:max-height (- (nth 3 edges) (nth 1 edges)))))
(inhibit-read-only t)