From 8df055c37faff827a7659947d5d170a62f95a398 Mon Sep 17 00:00:00 2001 From: Eshel Yaron Date: Sun, 27 Apr 2025 11:52:06 +0200 Subject: [PATCH] ; Update lisp/ldefs-boot.el --- lisp/ldefs-boot.el | 116 ++++++++++++++++++++++++++++++--------------- 1 file changed, 79 insertions(+), 37 deletions(-) diff --git a/lisp/ldefs-boot.el b/lisp/ldefs-boot.el index 215e1633bdb..e3718535038 100644 --- a/lisp/ldefs-boot.el +++ b/lisp/ldefs-boot.el @@ -11697,10 +11697,16 @@ For adding local variables on the first line of a file, for example for settings like `lexical-binding, which must be specified there, use the `add-file-local-variable-prop-line' command instead. +If optional variable INTERACTIVE is non-nil, display a message telling +the user how to make the new value take effect. + (fn VARIABLE VALUE &optional INTERACTIVE)" t) (autoload 'delete-file-local-variable "files-x" "\ Delete all settings of file-local VARIABLE from the Local Variables list. +If optional variable INTERACTIVE is non-nil, display a message telling +the user how to make the new value take effect. + (fn VARIABLE &optional INTERACTIVE)" t) (autoload 'add-file-local-variable-prop-line "files-x" "\ Add file-local VARIABLE with its VALUE to the -*- line. @@ -11715,10 +11721,16 @@ then this function adds it. To add variables to the Local Variables list at the end of the file, use the `add-file-local-variable' command instead. +If optional variable INTERACTIVE is non-nil, display a message telling +the user how to make the new value take effect. + (fn VARIABLE VALUE &optional INTERACTIVE)" t) (autoload 'delete-file-local-variable-prop-line "files-x" "\ Delete all settings of file-local VARIABLE from the -*- line. +If optional variable INTERACTIVE is non-nil, display a message telling +the user how to make the new value take effect. + (fn VARIABLE &optional INTERACTIVE)" t) (autoload 'add-dir-local-variable "files-x" "\ Add directory-local VARIABLE with its VALUE and MODE to .dir-locals.el. @@ -12141,22 +12153,27 @@ lines. Make a Flymake diagnostic for LOCUS's region from BEG to END. LOCUS is a buffer object or a string designating a file name. -TYPE is a diagnostic symbol and TEXT is string describing the -problem detected in this region. DATA is any object that the -caller wishes to attach to the created diagnostic for later -retrieval with `flymake-diagnostic-data'. +TYPE is a diagnostic symbol (see Info Node `(Flymake)Flymake error +types') + +INFO is a description of the problem detected. It may be a string, or +list (ORIGIN CODE MESSAGE) appropriately categorizing and describing the +diagnostic. ORIGIN may be a string or nil. CODE maybe be a string, a +number or nil. MESSAGE must be a string. -If LOCUS is a buffer BEG and END should be buffer positions -inside it. If LOCUS designates a file, BEG and END should be a -cons (LINE . COL) indicating a file position. In this second -case, END may be omitted in which case the region is computed -using `flymake-diag-region' if the diagnostic is appended to an -actual buffer. +DATA is any object that the caller wishes to attach to the created +diagnostic for later retrieval with `flymake-diagnostic-data'. -OVERLAY-PROPERTIES is an alist of properties attached to the -created diagnostic, overriding the default properties and any -properties listed in the `flymake-overlay-control' property of -the diagnostic's type symbol. +If LOCUS is a buffer, BEG and END should be buffer positions inside it. +If LOCUS designates a file, BEG and END should be a cons (LINE . COL) +indicating a file position. In this second case, END may be omitted in +which case the region is computed using `flymake-diag-region' if the +diagnostic is appended to an actual buffer. + +OVERLAY-PROPERTIES is an alist of properties attached to the created +diagnostic, overriding the default properties and any properties listed +in the `flymake-overlay-control' property of the diagnostic's type +symbol. FIX-FUNCTION, if non-nil, is a function that takes DATA and returns a list of fix suggestions for this diagnostic. Each fix suggestion is a @@ -12165,7 +12182,7 @@ is a list of edits in the format that `refactor-apply-edits' expects. Alternatively, EDITS can also be a function of no arguments that performs the fix. -(fn LOCUS BEG END TYPE TEXT &optional DATA OVERLAY-PROPERTIES FIX-FUNCTION)") +(fn LOCUS BEG END TYPE INFO &optional DATA OVERLAY-PROPERTIES FIX-FUNCTION)") (autoload 'flymake-diagnostics "flymake" "\ Get Flymake diagnostics in region determined by BEG and END. @@ -12180,6 +12197,10 @@ If COL is nil, return a region just for LINE. Return nil if the region is invalid. This function saves match data. (fn BUFFER LINE &optional COL)") +(autoload 'flymake-enable-backend "flymake" "\ +Enable Flymake BACKEND. + +(fn BACKEND)") (autoload 'flymake-mode "flymake" "\ Toggle Flymake mode on or off. @@ -26293,18 +26314,13 @@ it loads the previous minibuffer histories from `savehist-file'. The variable `savehist-autosave-interval' controls the periodicity of saving minibuffer histories. -If `savehist-save-minibuffer-history' is non-nil (the default), -all recorded minibuffer histories will be saved. You can arrange +All recorded minibuffer histories will be saved. You can arrange for additional history variables to be saved and restored by customizing `savehist-additional-variables', which by default is an empty list. For example, to save the history of commands invoked via \\[execute-extended-command], add `command-history' to the list in `savehist-additional-variables'. -Alternatively, you could customize `savehist-save-minibuffer-history' -to nil, and add to `savehist-additional-variables' only those -history variables you want to save. - To ignore some history variables, add their symbols to the list in `savehist-ignored-variables'. @@ -28671,29 +28687,32 @@ disabled. (autoload 'string-edit "string-edit" "\ Switch to a new buffer to edit STRING. -When the user finishes editing (with \\\\[string-edit-done]), SUCCESS-CALLBACK -is called with the resulting string. -If the user aborts (with \\\\[string-edit-abort]), ABORT-CALLBACK (if any) is -called with no parameters. +Call MAJOR-MODE (defaulting to `string-edit-mode') to set up the new +buffer, and insert PROMPT (defaulting to nothing) at the start of the +buffer. + +When the user finishes editing (with \\\\[string-edit-done]), call +READ (defaulting to `identity') on the resulting string, omitting PROMPT if any. -PROMPT will be inserted at the start of the buffer, but won't be -included in the resulting string. If PROMPT is nil, no help text -will be inserted. +If READ returns without an error, quit the buffer and call +SUCCESS-CALLBACK on the result. + +If the user aborts (with \\\\[string-edit-abort]), +call ABORT-CALLBACK (if any) with no parameters. Also see `read-string-from-buffer'. -(fn PROMPT STRING SUCCESS-CALLBACK &key ABORT-CALLBACK)") +(fn PROMPT STRING SUCCESS-CALLBACK &key ABORT-CALLBACK MAJOR-MODE READ)") (autoload 'read-string-from-buffer "string-edit" "\ Switch to a new buffer to edit STRING in a recursive edit. The user finishes editing with \\\\[string-edit-done], or aborts with \\\\[string-edit-abort]). -PROMPT will be inserted at the start of the buffer, but won't be -included in the resulting string. If nil, no prompt will be -inserted in the buffer. +Insert PROMPT at the start of the buffer. If nil, no prompt is +inserted. -When the user exits recursive edit, this function returns the -edited STRING. +When the user exits recursive edit, return the contents of the +buffer (without including PROMPT). Also see `string-edit'. @@ -28913,6 +28932,10 @@ This construct can only be used with lexical binding. (fn NAME BINDINGS &rest BODY)" nil t) (function-put 'named-let 'lisp-indent-function 2) +(autoload 'work-buffer--release "subr-x" "\ +Release work BUFFER. + +(fn BUFFER)") (autoload 'with-work-buffer "subr-x" "\ Create a work buffer, and evaluate BODY there like `progn'. Like `with-temp-buffer', but reuse an already created temporary @@ -31622,9 +31645,26 @@ of `define-treesit-generic-mode'. (autoload 'treesit-generic-mode-setup "treesit-x" "\ Go into the treesit generic mode MODE. -(fn LANG SOURCE)") +(fn LANG)") (register-definition-prefixes "treesit-x" '("alpinejs-generic-ts-" "gitattributes-generic-ts-mode" "liquid-generic-ts-mode" "treesit-generic-mode-font-lock-")) + +;;; Generated autoloads from trust.el + +(autoload 'trust-trusted-content-p "trust" "\ +Return non-nil if we trust the contents of the current buffer. +Here, \"trust\" means that we are willing to run code found inside of it. +See also `trust--trusted-content'.") +(autoload 'trust-set-buffer-trust "trust" "\ + + +(fn &optional BUF TRUST)" t) +(autoload 'trust-set-file-trust "trust" "\ + + +(fn FILE &optional TRUST)" t) +(register-definition-prefixes "trust" '("trust-")) + ;;; Generated autoloads from tty-tip.el @@ -32931,6 +32971,8 @@ For modern merging-based version control systems: backend with which to register the fileset. If every work file in the VC fileset is either added or modified, pop up a *vc-log* buffer to commit the fileset changes. + (If some are added or modified and some are unregistered, offer to + register the unregistered ones, first.) For a centralized version control system, if any work file in the VC fileset is out of date, offer to update the fileset. @@ -33353,7 +33395,7 @@ age, and everything that is older than that is shown in blue. If MOVE-POINT-TO is given, move the point to that line. -If VC-BK is given used that VC backend. +If BACKEND is given, use that VC backend. Customization variables: @@ -33364,7 +33406,7 @@ mode-specific menu. `vc-annotate-color-map' and `vc-annotate-background-mode' specifies whether the color map should be applied to the background or to the foreground. -(fn FILE REV &optional DISPLAY-MODE BUF MOVE-POINT-TO VC-BK)" t) +(fn FILE REV &optional DISPLAY-MODE BUF MOVE-POINT-TO BACKEND)" t) (register-definition-prefixes "vc-annotate" '("vc-")) -- 2.39.5