diff options
Diffstat (limited to 'doc/emacs/misc.texi')
| -rw-r--r-- | doc/emacs/misc.texi | 80 |
1 files changed, 51 insertions, 29 deletions
diff --git a/doc/emacs/misc.texi b/doc/emacs/misc.texi index 48bc69456ad..8f9ee317080 100644 --- a/doc/emacs/misc.texi +++ b/doc/emacs/misc.texi @@ -399,18 +399,18 @@ vulnerable to a variety of attacks, and you may want to avoid using these if what you're doing requires higher security. (This is the @code{ssl} check in @code{network-security-protocol-checks}). +@item Triple DES (or @acronym{3DES}) cipher +The @acronym{3DES} stream cipher provides at most 112 bits of +effective security, and a major security vulnerability in it was +disclosed in 2016 (CVE-2016-2183). It has been deprecated by NIST in +all applications from late 2023 onwards. (This is the +@code{3des-cipher} check in @code{network-security-protocol-checks}). @end table If @code{network-security-level} is @code{high}, the following checks will be made, in addition to the above: @table @asis -@item @acronym{3DES} cipher -The @acronym{3DES} stream cipher provides at most 112 bits of -effective security, which is considered to be towards the low end. -(This is the @code{3des} check in -@code{network-security-protocol-checks}). - @item a validated certificate changes the public key Servers change their keys occasionally, and that is normally nothing to be concerned about. However, if you are worried that your network @@ -1810,31 +1810,28 @@ you can give each daemon its own server name like this: emacs --daemon=foo @end example -@findex server-stop-automatically +@vindex server-stop-automatically The Emacs server can optionally be stopped automatically when -certain conditions are met. To do this, call the function -@code{server-stop-automatically} in your init file (@pxref{Init -File}), with one of the following arguments: - -@itemize -@item -With the argument @code{empty}, the server is stopped when it has no -clients, no unsaved file-visiting buffers and no running processes -anymore. - -@item -With the argument @code{delete-frame}, when the last client frame is -being closed, you are asked whether each unsaved file-visiting buffer -must be saved and each unfinished process can be stopped, and if so, -the server is stopped. +certain conditions are met. To do this, set the option +@code{server-stop-automatically} to one of the following values: -@item -With the argument @code{kill-terminal}, when the last client frame is -being closed with @kbd{C-x C-c} (@code{save-buffers-kill-terminal}), -you are asked whether each unsaved file-visiting buffer must be saved -and each unfinished process can be stopped, and if so, the server is +@table @code +@item empty +This value causes the server to be stopped when it has no clients, no +unsaved file-visiting buffers and no running processes anymore. + +@item delete-frame +This value means that when the last client frame is being closed, you +are asked whether each unsaved file-visiting buffer must be saved and +each unfinished process can be stopped, and if so, the server is stopped. -@end itemize + +@item kill-terminal +This value means that when the last client frame is being closed with +@kbd{C-x C-c} (@code{save-buffers-kill-terminal}), you are asked +whether each unsaved file-visiting buffer must be saved and each +unfinished process can be stopped, and if so, the server is stopped. +@end table @findex server-eval-at If you have defined a server by a unique server name, it is possible @@ -2081,6 +2078,18 @@ files. When this option is given, the arguments to @command{emacsclient} are interpreted as a list of expressions to evaluate, @emph{not} as a list of files to visit. +@vindex server-eval-args-left +Passing complex Lisp expression via the @option{--eval} command-line +option sometimes requires elaborate escaping of characters special to +the shell. To avoid this, you can pass arguments to Lisp functions in +your expression as additional separate arguments to +@command{emacsclient}, and use @var{server-eval-args-left} in the +expression to access those arguments. Be careful to have your +expression remove the processed arguments from +@var{server-eval-args-left} regardless of whether your code succeeds, +for example by using @code{pop}, otherwise Emacs will attempt to +evaluate those arguments as separate Lisp expressions. + @item -f @var{server-file} @itemx --server-file=@var{server-file} Specify a server file (@pxref{TCP Emacs server}) for connecting to an @@ -2815,9 +2824,13 @@ frame parameters you don't want to be restored; they will then be set according to your customizations in the init file. @vindex desktop-files-not-to-save +@vindex remote-file-name-access-timeout Information about buffers visiting remote files is not saved by default. Customize the variable @code{desktop-files-not-to-save} to -change this. +change this. In this case, you might also consider customizing +@code{remote-file-name-access-timeout}, which is the number of +seconds after which buffer restoration of a remote file is +stopped. This prevents Emacs being blocked. @vindex desktop-restore-eager By default, all the buffers in the desktop are restored in one go. @@ -2996,6 +3009,15 @@ buffer, and lets you navigate to those pages by hitting @kbd{RET}. It is bound to @kbd{H}. +@vindex xwidget-webkit-disable-javascript +@cindex disabling javascript in webkit buffers + JavaScript is enabled by default inside WebKit buffers, which could be +undesirable, as Web sites often use it to track your online activity. +You can disable JavaScript in WebKit buffers by customizing the variable +@code{xwidget-webkit-disable-javascript} to a non-@code{nil} value. +You must kill all WebKit buffers for this setting to take effect, after +it is changed. + @node Browse-URL @subsection Following URLs @cindex World Wide Web |