Spelling fixes
This commit is contained in:
Paul Eggert
parent
636461686f
commit
3dcac22dd4
47 changed files with 65 additions and 65 deletions
|
|
@ -222922,7 +222922,7 @@
|
|||
|
||||
2016-07-09 Jürgen Hötzel <juergen@archlinux.org>
|
||||
|
||||
Wrap around error in coreutil's ls
|
||||
Wrap around error in coreutils ls
|
||||
|
||||
* lisp/net/tramp-sh.el (tramp-sh-handle-insert-directory): Add switch
|
||||
"--quoting-style=literal" if remote host supports quoting style.
|
||||
|
|
|
|||
|
|
@ -81723,7 +81723,7 @@
|
|||
|
||||
* src/xfns.c (x_make_gc): Don't set FillOpaqueStippled on cursor
|
||||
GC. The reason is that some X servers break on such a fill
|
||||
style if the operation being performed is not a stiple
|
||||
style if the operation being performed is not a stipple
|
||||
operation.
|
||||
|
||||
2022-02-09 Po Lu <luangruo@yahoo.com>
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ views.
|
|||
People are sometimes discouraged from participating in GNU development
|
||||
because of certain patterns of communication that strike them as
|
||||
unfriendly, unwelcoming, rejecting, or harsh. This discouragement
|
||||
particularly affects members of disprivileged demographics, but it is
|
||||
particularly affects members of unprivileged demographics, but it is
|
||||
not limited to them. Therefore, we ask all contributors to make a
|
||||
conscious effort, in GNU Project discussions, to communicate in ways
|
||||
that avoid that outcome — to avoid practices that will predictably and
|
||||
|
|
|
|||
|
|
@ -2354,7 +2354,7 @@ window within a frame can also switch the selected window. @xref{Mouse
|
|||
Window Auto-selection}, which describes the behavior for different
|
||||
values. When the mouse is moved over a new window, a focus event for
|
||||
switching windows is generated. Focus events for windows are
|
||||
reperesented in Lisp as lists that look like this:
|
||||
represented in Lisp as lists that look like this:
|
||||
|
||||
@example
|
||||
(select-window @var{new-window})
|
||||
|
|
|
|||
|
|
@ -1582,7 +1582,7 @@ Here's an example @var{treesit-thing-settings} for C and C++:
|
|||
@end example
|
||||
|
||||
@noindent
|
||||
Note that this example is modified for didactical purposes, and isn't
|
||||
Note that this example is modified for didactic purposes, and isn't
|
||||
exactly how C and C@t{++} modes define things.
|
||||
@end defvar
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ from regular expressions (@pxref{Regular Expressions}) to full
|
|||
left-to-right (a.k.a.@: @acronym{LL}) grammar parsers (@pxref{Top,,
|
||||
Bovine parser development,bovine}). @dfn{Parsing Expression Grammars}
|
||||
(@acronym{PEG}) are another approach to text parsing that offer more
|
||||
structure and composibility than regular expressions, but less
|
||||
structure and composability than regular expressions, but less
|
||||
complexity than context-free grammars.
|
||||
|
||||
A Parsing Expression Grammar (@acronym{PEG}) describes a formal language
|
||||
|
|
|
|||
|
|
@ -1549,7 +1549,7 @@ also specify the absolute path to the program, e.g.@:
|
|||
program whose file name would be interpreted as an explicitly-remote
|
||||
command, you can use @kbd{/:} to quote the name, e.g.@:
|
||||
@samp{/:/ssh:user@@remote:whoami} (@pxref{Quoted File Names,,, emacs,
|
||||
The GNU Emacs Manual}). To disable explicity-remote commands entirely,
|
||||
The GNU Emacs Manual}). To disable explicitly-remote commands entirely,
|
||||
you can set the option @code{eshell-explicit-remote-commands} to
|
||||
@code{nil}.
|
||||
|
||||
|
|
|
|||
|
|
@ -1251,7 +1251,7 @@ value in some other application.
|
|||
:END:
|
||||
|
||||
#+findex: modus-themes-get-color-value
|
||||
The fuction ~modus-themes-get-color-value~ can be called from Lisp to
|
||||
The function ~modus-themes-get-color-value~ can be called from Lisp to
|
||||
return the value of a color from the active Modus theme palette. It
|
||||
takea a =COLOR= argument and an optional =OVERRIDES=. It also accepts
|
||||
a third =THEME= argument, to get the color from the given theme.
|
||||
|
|
@ -2162,7 +2162,7 @@ until version 4.3.0.
|
|||
;; was the default in versions of the Modus themes before 4.4.0
|
||||
(setq modus-themes-common-palette-overrides
|
||||
'((bg-prose-block-contents unspecified)
|
||||
(bg-prose-block-delimiter unspeficied)
|
||||
(bg-prose-block-delimiter unspecified)
|
||||
(fg-prose-block-delimiter fg-dim)))
|
||||
#+end_src
|
||||
|
||||
|
|
@ -2806,7 +2806,7 @@ above:
|
|||
The reason we no longer provide this option is because it depends on a
|
||||
non-~nil~ value for ~x-underline-at-descent-line~. That variable
|
||||
affects ALL underlines, including those of links. The effect is
|
||||
intrusive and looks awkard in prose.
|
||||
intrusive and looks awkward in prose.
|
||||
|
||||
As such, the Modus themes no longer provide that option but instead
|
||||
offer this piece of documentation to make the user fully aware of the
|
||||
|
|
@ -3160,7 +3160,7 @@ specification of that variable looks like this:
|
|||
|
||||
With the exception of ~org-verbatim~ and ~org-code~ faces, everything else
|
||||
uses the corresponding type of emphasis: a bold typographic weight, or
|
||||
italicised, underlined, and struck through text.
|
||||
italicized, underlined, and struck through text.
|
||||
|
||||
The best way for users to add some extra attributes, such as a
|
||||
foreground color, is to define their own faces and assign them to the
|
||||
|
|
@ -5074,7 +5074,7 @@ more effective than trying to do the same with either red or blue (the
|
|||
latter is the least effective in that regard).
|
||||
|
||||
When we need to work with several colors, it is always better to have
|
||||
sufficient manoeuvring space, especially since we cannot pick arbitrary
|
||||
sufficient maneuvering space, especially since we cannot pick arbitrary
|
||||
colors but only those that satisfy the accessibility objectives of the
|
||||
themes.
|
||||
|
||||
|
|
@ -5128,7 +5128,7 @@ each of the three channels of light (red, green, blue). For example:
|
|||
: xrandr --output LVDS1 --brightness 1.0 --gamma 0.76:0.75:0.68
|
||||
|
||||
Typography is another variable. Some font families are blurry at small
|
||||
point sizes. Others may have a regular weight that is lighter (thiner)
|
||||
point sizes. Others may have a regular weight that is lighter (thinner)
|
||||
than that of their peers which may, under certain circumstances, cause a
|
||||
halo effect around each glyph.
|
||||
|
||||
|
|
@ -5180,7 +5180,7 @@ it is already understood that one must follow the indicator or headline
|
|||
to view its contents and (ii) underlining everything would make the
|
||||
interface virtually unusable.
|
||||
|
||||
Again, one must exercise judgement in order to avoid discrimination,
|
||||
Again, one must exercise judgment in order to avoid discrimination,
|
||||
where "discrimination" refers to:
|
||||
|
||||
+ The treatment of substantially different magnitudes as if they were of
|
||||
|
|
@ -5254,7 +5254,7 @@ the themes, which is partially fleshed out in this manual.
|
|||
|
||||
With regard to the artistic aspect (where "art" qua skill may amount to
|
||||
an imprecise science), there is no hard-and-fast rule in effect as it
|
||||
requires one to exercize discretion and make decisions based on
|
||||
requires one to exercise discretion and make decisions based on
|
||||
context-dependent information or constraints. As is true with most
|
||||
things in life, when in doubt, do not cling on to the letter of the law
|
||||
but try to understand its spirit.
|
||||
|
|
|
|||
|
|
@ -1210,7 +1210,7 @@ described below. If you use the latter approach, you can use the
|
|||
transform them from the convenient to the expected form.
|
||||
|
||||
If you explicitly specify children and then transform them using
|
||||
@code{:setup-chilren}, then the class of the group is determined as usual,
|
||||
@code{:setup-children}, then the class of the group is determined as usual,
|
||||
based on explicitly specified children.
|
||||
|
||||
If you do not explicitly specify children and thus rely solely on
|
||||
|
|
|
|||
|
|
@ -1389,7 +1389,7 @@ color that is combined with FG-FOR-BG."
|
|||
:foreground fg
|
||||
:weight
|
||||
;; If we have `bold' specifically, we inherit the face of
|
||||
;; the same name. This allows the user to customise that
|
||||
;; the same name. This allows the user to customize that
|
||||
;; face, such as to change its font family.
|
||||
(if (and weight (not (eq weight 'bold)))
|
||||
weight
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ along with GNU Emacs. If not, see <https://www.gnu.org/licenses/>. -->
|
|||
<!-- targetSandboxVersion must be 1, for otherwise fascist security
|
||||
restrictions prevent Emacs from making HTTP connections.
|
||||
|
||||
Futhermore, versionCode should remain constant, rather than increase
|
||||
Furthermore, versionCode should remain constant, rather than increase
|
||||
with each major release, because it is impossible to downgrade an
|
||||
installation with a greater value to an older version of Emacs. -->
|
||||
|
||||
|
|
|
|||
|
|
@ -170,7 +170,7 @@ In normal circumstances, Emacs should automatically detect and configure
|
|||
one of the C++ standard libraries part of the NDK when such a library is
|
||||
required to build a dependency specified under `--with-ndk-path'.
|
||||
|
||||
Nevertheless, this process is not infalliable, and with certain versions
|
||||
Nevertheless, this process is not infallible, and with certain versions
|
||||
of the NDK is liable to fail to locate a C++ compiler, requiring that
|
||||
you run the `make_standalone_toolchain.py' script in the NDK
|
||||
distribution to create a ``standalone toolchain'' and substitute the
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ public final class EmacsDesktopNotification
|
|||
notification. */
|
||||
public final String[] actions, titles;
|
||||
|
||||
/* Delay in miliseconds after which this notification should be
|
||||
/* Delay in milliseconds after which this notification should be
|
||||
automatically dismissed. */
|
||||
public final long delay;
|
||||
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ public final class EmacsGC extends EmacsHandleObject
|
|||
public EmacsPixmap clip_mask, stipple;
|
||||
public Paint gcPaint;
|
||||
|
||||
/* Drawable object for rendering the stiple bitmap. */
|
||||
/* Drawable object for rendering the stipple bitmap. */
|
||||
public EmacsTileObject tileObject;
|
||||
|
||||
/* ID incremented every time the clipping rectangles of any GC
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@
|
|||
import android.graphics.Rect;
|
||||
import android.graphics.Shader.TileMode;
|
||||
|
||||
/* This is a crude facsimilie of the BitmapDrawable class implementing
|
||||
/* This is a crude facsimile of the BitmapDrawable class implementing
|
||||
just enough of its functionality to support displaying stipples in
|
||||
EmacsGC. */
|
||||
|
||||
|
|
|
|||
|
|
@ -137,7 +137,7 @@ interface WindowConsumer
|
|||
/* Don't attach this window to CONSUMER if incompatible. */
|
||||
&& isWindowEligible (consumer, window))
|
||||
{
|
||||
/* Permantly bind this window to the consumer. */
|
||||
/* Permanently bind this window to the consumer. */
|
||||
window.attachmentToken = consumer.getAttachmentToken ();
|
||||
window.previouslyAttached = true;
|
||||
consumer.attachWindow (window);
|
||||
|
|
@ -166,7 +166,7 @@ && isWindowEligible (consumer, window))
|
|||
if (consumer.getAttachedWindow () == null
|
||||
&& isWindowEligible (consumer, window))
|
||||
{
|
||||
/* Permantly bind this window to the consumer. */
|
||||
/* Permanently bind this window to the consumer. */
|
||||
window.attachmentToken = consumer.getAttachmentToken ();
|
||||
window.previouslyAttached = true;
|
||||
consumer.attachWindow (window);
|
||||
|
|
@ -186,7 +186,7 @@ && isWindowEligible (consumer, window))
|
|||
intent.addFlags (Intent.FLAG_ACTIVITY_NEW_TASK);
|
||||
|
||||
/* Intent.FLAG_ACTIVITY_NEW_DOCUMENT is lamentably unavailable on
|
||||
older systems than Lolipop. */
|
||||
older systems than Lollipop. */
|
||||
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP)
|
||||
{
|
||||
intent.addFlags (Intent.FLAG_ACTIVITY_NEW_DOCUMENT
|
||||
|
|
|
|||
|
|
@ -465,7 +465,7 @@ completions list."
|
|||
(funcall efn string status)))))
|
||||
;; The predicate is meant for the original completion
|
||||
;; candidates, which may be symbols or cons cells, but
|
||||
;; now we only have strings, so it might be unapplicable.
|
||||
;; now we only have strings, so it might not be applicable.
|
||||
(props (plist-put props :predicate nil))
|
||||
(completion-at-point-functions
|
||||
(list (lambda () `(,beg ,end ,col ,@props)))))
|
||||
|
|
|
|||
|
|
@ -207,7 +207,7 @@ Useful to hook into pass checkers.")
|
|||
;; cl-macs.el. We can't use `cl-deftype-satisfies' directly as the
|
||||
;; relation type <-> predicate is not bijective (bug#45576).
|
||||
(defconst comp-known-predicates
|
||||
;; FIXME: Auto-generate (most of) it from `cl-deftype-satifies'?
|
||||
;; FIXME: Auto-generate (most of) it from `cl-deftype-satisfies'?
|
||||
'((arrayp array)
|
||||
(atom atom)
|
||||
(bool-vector-p bool-vector)
|
||||
|
|
|
|||
|
|
@ -2646,7 +2646,7 @@ will be deleted."
|
|||
(message "Nothing to autoremove")))))
|
||||
|
||||
(defun package-isolate (packages &optional temp-init)
|
||||
"Start an uncustomised Emacs and only load a set of PACKAGES.
|
||||
"Start an uncustomized Emacs and only load a set of PACKAGES.
|
||||
If TEMP-INIT is non-nil, or when invoked with a prefix argument,
|
||||
the Emacs user directory is set to a temporary directory."
|
||||
(interactive
|
||||
|
|
|
|||
|
|
@ -177,7 +177,7 @@ This is used to try and detect cases where buffer modifications are \"lost\".")
|
|||
;; presume that these might be too old to receive fixes, so better not
|
||||
;; annoy the user too much about errors.
|
||||
(string-match "\\..*\\." emacs-version)
|
||||
"If non-nil, keep track of errors in `before/after-chage-functions' calls.
|
||||
"If non-nil, keep track of errors in `before/after-change-functions' calls.
|
||||
The errors are kept in `track-changes--error-log'.")
|
||||
|
||||
(cl-defun track-changes-register ( signal &key nobefore disjoint immediate)
|
||||
|
|
@ -500,9 +500,9 @@ Details logged to `track-changes--error-log'")
|
|||
|
||||
(if track-changes--before-clean
|
||||
(progn
|
||||
;; Detect disjointness with previous changes here as well,
|
||||
;; Detect disjointedness with previous changes here as well,
|
||||
;; so that if a client calls `track-changes-fetch' all the time,
|
||||
;; it doesn't prevent others from getting a disjointness signal.
|
||||
;; it doesn't prevent others from getting a disjointedness signal.
|
||||
(when (and track-changes--before-beg
|
||||
(let ((found nil))
|
||||
(dolist (tracker track-changes--disjoint-trackers)
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ This includes when running `eshell-command'."
|
|||
t))))
|
||||
|
||||
(defun eshell--source-file (file &optional args subcommand-p)
|
||||
"Return a Lisp form for executig the Eshell commands in FILE, passing ARGS.
|
||||
"Return a Lisp form for executing the Eshell commands in FILE, passing ARGS.
|
||||
If SUBCOMMAND-P is non-nil, execute this as a subcommand."
|
||||
(let ((cmd (eshell-parse-command `(:file . ,file))))
|
||||
(when subcommand-p
|
||||
|
|
|
|||
|
|
@ -150,7 +150,7 @@ slot, passing the exit status of the redirected command.
|
|||
If PASS-MODE is non-nil, Eshell will pass the redirection mode as an
|
||||
argument (which is the symbol `overwrite', `append' or `insert') to
|
||||
OUTPUT-FUNCTION, which should return the real output function (either an
|
||||
ordinary function or `eshell-generic-target' as desribed above)."
|
||||
ordinary function or `eshell-generic-target' as described above)."
|
||||
:version "30.1"
|
||||
:type '(repeat
|
||||
(list (string :tag "Target")
|
||||
|
|
|
|||
|
|
@ -568,7 +568,7 @@ loaded."
|
|||
(rotation (plist-get props :rotation)))
|
||||
(cond
|
||||
;; The scale of the image won't be available until
|
||||
;; `image_set_transform', and as such, defer to its judgement.
|
||||
;; `image_set_transform', and as such, defer to its judgment.
|
||||
((eq scaling 'default) 'lambda)
|
||||
;; We always smooth when scaling down and small upwards scaling.
|
||||
((and scaling (< scaling 2))
|
||||
|
|
@ -812,7 +812,7 @@ where FILE is the file from which to load the image, and DATA is a
|
|||
string containing the actual image data. If the property `:type TYPE'
|
||||
is omitted or nil, try to determine the image type from its first few
|
||||
bytes of image data. If that doesn't work, and the property `:file
|
||||
FILE' provide a file name, use its file extension as idication of the
|
||||
FILE' provide a file name, use its file extension as indication of the
|
||||
image type. If `:type TYPE' is provided, it must match the actual type
|
||||
determined for FILE or DATA by `create-image'.
|
||||
|
||||
|
|
|
|||
|
|
@ -1424,7 +1424,7 @@ via `dictionary-dictionaries'."
|
|||
;; This function runs from the tooltip timer. We don't want to
|
||||
;; signal errors from the timer due to "Unknown server answers",
|
||||
;; we prefer not to show anything in that case. FIXME: Perhaps
|
||||
;; use with-demoted-errors, to show the unknonw answers in the
|
||||
;; use with-demoted-errors, to show the unknown answers in the
|
||||
;; echo-area?
|
||||
(ignore-errors
|
||||
(let* ((word (dictionary-word-at-mouse-event
|
||||
|
|
|
|||
|
|
@ -2463,7 +2463,7 @@ If ERROR-OUT, signal user-error if there are no bookmarks."
|
|||
|
||||
(defun eww-save-history ()
|
||||
"Save the current page's data to the history.
|
||||
If the current page is a historial one loaded from
|
||||
If the current page is a historical one loaded from
|
||||
`eww-history' (e.g. by calling `eww-back-url'), this will update the
|
||||
page's entry in `eww-history' and return nil. Otherwise, add a new
|
||||
entry to `eww-history' and return t."
|
||||
|
|
|
|||
|
|
@ -168,7 +168,7 @@ If it is nil, the default context will be used."
|
|||
|
||||
;;;###tramp-autoload
|
||||
(defcustom tramp-distrobox-program "distrobox"
|
||||
"Name of the Distrobxx client program."
|
||||
"Name of the Distrobox client program."
|
||||
:group 'tramp
|
||||
:version "30.1"
|
||||
:type '(choice (const "distrobox")
|
||||
|
|
|
|||
|
|
@ -2705,7 +2705,7 @@ The method used must be an out-of-band method."
|
|||
(let ((dired (tramp-get-ls-command-with v "--dired")))
|
||||
(when (stringp switches)
|
||||
(setq switches (split-string switches)))
|
||||
;; Newer coreutil versions of ls (9.5 and up) imply long format
|
||||
;; Newer coreutils versions of ls (9.5 and up) imply long format
|
||||
;; output when "--dired" is given. Suppress this implicit rule.
|
||||
(when dired
|
||||
(let ((tem switches)
|
||||
|
|
|
|||
|
|
@ -4851,7 +4851,7 @@ a connection-local variable."
|
|||
(defvar tramp-direct-async-process nil
|
||||
"Whether direct asynchronous processes should be used.
|
||||
It is not recommended to change this variable globally. Instead, it
|
||||
should be set conmnection-local.")
|
||||
should be set connection-local.")
|
||||
|
||||
(defun tramp-direct-async-process-p (&rest args)
|
||||
"Whether direct async `make-process' can be called."
|
||||
|
|
|
|||
|
|
@ -1726,7 +1726,7 @@ under `outline-minor-mode' is reverted by `revert-buffer'."
|
|||
|
||||
(defun outline-revert-buffer-rehighlight ()
|
||||
"Rehighlight outlines when reverting buffer under `outline-minor-mode'.
|
||||
This function rehighlightes outlines after the buffer under
|
||||
This function rehighlights outlines after the buffer under
|
||||
`outline-minor-mode' is reverted by `revert-buffer' when font-lock
|
||||
can't update highlighting for `outline-minor-mode-highlight'."
|
||||
(when (and outline-minor-mode-highlight
|
||||
|
|
|
|||
|
|
@ -291,7 +291,7 @@ and /* */ comments. SOFT works the same as in
|
|||
;; I want to experiment with explicitly listing out all each cases and
|
||||
;; handle them separately, as opposed to fiddling with `comment-start'
|
||||
;; and friends. This will have more duplicate code and will be less
|
||||
;; generic, but in the same time might save us from writting cryptic
|
||||
;; generic, but in the same time might save us from writing cryptic
|
||||
;; code to handle all sorts of edge cases.
|
||||
;;
|
||||
;; For this command, let's try to make it basic: if the current line
|
||||
|
|
|
|||
|
|
@ -188,7 +188,7 @@ See `flymake-error-bitmap' and `flymake-warning-bitmap'."
|
|||
The value can be nil (don't indicate errors but just highlight them),
|
||||
fringes (use fringes) or margins (use margins)
|
||||
|
||||
Difference between fringes and margin is that fringes support diplaying
|
||||
Difference between fringes and margin is that fringes support displaying
|
||||
bitmaps on graphical displays and margins display text in a blank area
|
||||
from current buffer that works in both graphical and text displays.
|
||||
|
||||
|
|
@ -788,7 +788,7 @@ Return to original margin width if ORIG-WIDTH is non-nil."
|
|||
left-margin-width 2)
|
||||
(setq-local flymake--original-margin-width right-margin-width
|
||||
right-margin-width 2))))
|
||||
;; Apply margin to all windows avalaibles
|
||||
;; Apply margin to all windows available.
|
||||
(mapc (lambda (x)
|
||||
(set-window-buffer x (window-buffer x)))
|
||||
(get-buffer-window-list nil nil 'visible))))
|
||||
|
|
|
|||
|
|
@ -2117,7 +2117,7 @@ Such as the current syntax table and the applied syntax properties."
|
|||
;; Using the temporary buffer is both a performance and a buffer
|
||||
;; management optimization.
|
||||
(with-current-buffer tmp-buffer
|
||||
;; This let is fairly dangerouns, but improves performance
|
||||
;; This let is fairly dangerous, but improves performance
|
||||
;; for large lists, see https://debbugs.gnu.org/53749#227
|
||||
(let ((inhibit-modification-hooks t))
|
||||
(erase-buffer)
|
||||
|
|
|
|||
|
|
@ -305,7 +305,7 @@ names which represent them."
|
|||
(new-uri-list nil)
|
||||
(dnd-unescape-file-uris t))
|
||||
(dolist (uri uri-list)
|
||||
;; If the URI is a preprepared file name, insert it directly.
|
||||
;; If the URI is a prepared file name, insert it directly.
|
||||
(if (string-match-p "^/content/by-authority\\(-named\\)?/" uri)
|
||||
(setq uri (concat "file:" uri)
|
||||
dnd-unescape-file-uris nil)
|
||||
|
|
|
|||
|
|
@ -792,7 +792,7 @@ Signal an error if the entire string was not used."
|
|||
|
||||
(defvar thing-at-point-hexadecimal-regexp
|
||||
"\\(0x\\|#x\\)\\([a-fA-F0-9]+\\)"
|
||||
"A regexp matchin a hexadecimal number.")
|
||||
"A regexp matching a hexadecimal number.")
|
||||
|
||||
;;;###autoload
|
||||
(defun number-at-point ()
|
||||
|
|
|
|||
|
|
@ -3645,7 +3645,7 @@ have a history of their own.")
|
|||
(propertize "\n" 'face face 'line-height t))))
|
||||
|
||||
(defmacro transient-with-shadowed-buffer (&rest body)
|
||||
"While in the transient buffer, temporarly make the shadowed buffer current."
|
||||
"While in the transient buffer, temporarily make the shadowed buffer current."
|
||||
(declare (indent 0) (debug t))
|
||||
`(with-current-buffer (or transient--shadowed-buffer (current-buffer))
|
||||
,@body))
|
||||
|
|
|
|||
|
|
@ -830,7 +830,7 @@ t, nil, append, prepend, keep. See more in
|
|||
`treesit-font-lock-rules'.")
|
||||
|
||||
(defsubst treesit--font-lock-setting-feature (setting)
|
||||
"Reutrn the feature of SETTING.
|
||||
"Return the feature of SETTING.
|
||||
SETTING should be a setting in `treesit-font-lock-settings'."
|
||||
(nth 2 setting))
|
||||
|
||||
|
|
|
|||
|
|
@ -377,7 +377,7 @@ These characters are specified in RFC 3986, Appendix A.")
|
|||
(aset vec ?& nil)
|
||||
(aset vec ?\; nil)
|
||||
vec)
|
||||
"Allowed-charcter byte mask for keys and values in the query segment of a URI.
|
||||
"Allowed-character byte mask for keys and values in the query segment of a URI.
|
||||
url-query-allowed-chars minus '=', '&', and ';'.")
|
||||
|
||||
;;;###autoload
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@
|
|||
;; like to also generally make tool bars better.
|
||||
;;
|
||||
;; Targeting 0.3:
|
||||
;; * Properly support reamining less frequently used tool bar item specs. From
|
||||
;; * Properly support remaining less frequently used tool bar item specs. From
|
||||
;; `parse_tool_bar_item':
|
||||
;; * :visible
|
||||
;; * :filter
|
||||
|
|
@ -102,7 +102,7 @@
|
|||
;; lot of garbage. So this benchmarking focuses on garbage
|
||||
;; generation. Since it has to run after most commands, generating
|
||||
;; significantly more garbage will cause noticeable performance
|
||||
;; degration.
|
||||
;; degradation.
|
||||
;;
|
||||
;; The refresh has two steps:
|
||||
;;
|
||||
|
|
@ -111,7 +111,7 @@
|
|||
;; bar string.
|
||||
;;
|
||||
;; Additionally, we keep track of the percentage of commands that
|
||||
;; acutally created a refresh.
|
||||
;; actually created a refresh.
|
||||
(defvar window-tool-bar--memory-use-delta-step1 (make-list 7 0)
|
||||
"Absolute delta of memory use counters during step 1.
|
||||
This is a list in the same structure as `memory-use-counts'.")
|
||||
|
|
|
|||
|
|
@ -945,7 +945,7 @@ keywords is understood:
|
|||
No more than three actions defined here will be
|
||||
displayed, not counting any with "default" as its
|
||||
key.
|
||||
:timeout Number of miliseconds from the display of the
|
||||
:timeout Number of milliseconds from the display of the
|
||||
notification at which it will be automatically
|
||||
dismissed, or a value of zero or smaller if it
|
||||
is to remain until user action is taken to dismiss
|
||||
|
|
|
|||
|
|
@ -5359,7 +5359,7 @@ hash_string (char const *ptr, ptrdiff_t len)
|
|||
hash = sxhash_combine (hash, c);
|
||||
}
|
||||
while (p + sizeof hash <= end);
|
||||
/* Hash the last wordful of bytes in the string, because that is
|
||||
/* Hash the last word's worth of bytes in the string, because that is
|
||||
is often the part where strings differ. This may cause some
|
||||
bytes to be hashed twice but we assume that's not a big problem. */
|
||||
EMACS_UINT c;
|
||||
|
|
|
|||
|
|
@ -1211,7 +1211,7 @@ itree_node_intersects (const struct itree_node *node,
|
|||
`ITER->begin..ITER->end`) so it will also return some nodes which aren't in
|
||||
that narrowing simply because they may have children which are.
|
||||
|
||||
The code itself is very unsatifactory because the code of each one
|
||||
The code itself is very unsatisfactory because the code of each one
|
||||
of the supported traversals seems completely different from the others.
|
||||
If someone knows how to make it more uniform and "obviously correct",
|
||||
please make yourself heard. */
|
||||
|
|
|
|||
|
|
@ -405,7 +405,7 @@ json_out_nest (json_out_t *jo)
|
|||
{
|
||||
--jo->maxdepth;
|
||||
if (jo->maxdepth < 0)
|
||||
error ("Maximum JSON serialisation depth exceeded");
|
||||
error ("Maximum JSON serialization depth exceeded");
|
||||
}
|
||||
|
||||
static void
|
||||
|
|
|
|||
|
|
@ -343,14 +343,14 @@ buffer before the macro is executed. */)
|
|||
restore Vexecuting_kbd_macro and executing_kbd_macro_index, and
|
||||
run 'kbd-macro-termination-hook'.
|
||||
|
||||
If read_char happens to be called at the end of a macro interation,
|
||||
If read_char happens to be called at the end of a macro iteration,
|
||||
but before read_key_sequence could handle the end (e.g., when lisp
|
||||
code calls 'read-event', 'read-char', or 'read-char-exclusive'),
|
||||
read_char will simply continue reading other available input
|
||||
(Bug#68272). Vexecuting_kbd_macro and executing_kbd_macro remain
|
||||
untouched until the end of the iteration is handled.
|
||||
|
||||
This is similar (in observable behavior) to a posibly simpler
|
||||
This is similar (in observable behavior) to a possibly simpler
|
||||
implementation of keyboard macros in which this function pushed all
|
||||
characters of the macro into the incoming event queue and returned
|
||||
immediately. Maybe this is the implementation that we ideally
|
||||
|
|
|
|||
|
|
@ -1130,7 +1130,7 @@ tim_sort (Lisp_Object predicate, Lisp_Object keyfunc,
|
|||
keys[i] = call1 (keyfunc, seq[i]);
|
||||
|
||||
/* FIXME: This is where we would check the keys for interesting
|
||||
properties for more optimised comparison (such as all being fixnums
|
||||
properties for more optimized comparison (such as all being fixnums
|
||||
etc). */
|
||||
|
||||
/* March over the array once, left to right, finding natural runs,
|
||||
|
|
|
|||
|
|
@ -19173,7 +19173,7 @@ try_scrolling (Lisp_Object window, bool just_this_one_p,
|
|||
/* Maybe forget recorded base line for line number display. */
|
||||
/* FIXME: Why do we need this? `try_scrolling` can only be called from
|
||||
`redisplay_window` which should have flushed this cache already when
|
||||
eeded. */
|
||||
needed. */
|
||||
if (!BASE_LINE_NUMBER_VALID_P (w))
|
||||
w->base_line_number = 0;
|
||||
|
||||
|
|
@ -35810,7 +35810,7 @@ note_fringe_highlight (struct frame *f, Lisp_Object window, int x, int y,
|
|||
|
||||
/* NOTE: iterating over glyphs can only find text properties coming
|
||||
from visible text. This means that zero-length overlays and
|
||||
invisibile text are NOT inspected. */
|
||||
invisible text are NOT inspected. */
|
||||
for (; glyph_num; glyph_num--, glyph++)
|
||||
{
|
||||
Lisp_Object pos = make_fixnum (glyph->charpos);
|
||||
|
|
|
|||
|
|
@ -157,7 +157,7 @@
|
|||
(search-forward "BlackOn")
|
||||
(should (eq (get-text-property (point) 'mouse-face)
|
||||
'erc-spoiler-face)))
|
||||
;; Start wtih ERC default face.
|
||||
;; Start with ERC default face.
|
||||
(erc-goodies-tests--assert-face
|
||||
0 "BEGIN " 'erc-default-face
|
||||
'(fg:erc-color-face0 bg:erc-color-face0))
|
||||
|
|
@ -168,7 +168,7 @@
|
|||
;; Masked in all black.
|
||||
(erc-goodies-tests--assert-face
|
||||
20 "BlackOnBlack" '(fg:erc-color-face1 bg:erc-color-face1) nil)
|
||||
;; Explicit "default" code ignoerd.
|
||||
;; Explicit "default" code ignored.
|
||||
(erc-goodies-tests--assert-face
|
||||
34 "Default" '(erc-default-face)
|
||||
'(fg:erc-color-face1 bg:erc-color-face1))
|
||||
|
|
|
|||
|
|
@ -199,7 +199,7 @@ resp. succeeded instead of signaling an error."
|
|||
|
||||
;; peg-ex-parse-int recognizes integers and computes the corresponding
|
||||
;; value. The grammar is the same as for `peg-ex-recognize-int'
|
||||
;; augmented with parsing actions. Unfortunaletly, the actions add
|
||||
;; augmented with parsing actions. Unfortunately, the actions add
|
||||
;; quite a bit of clutter.
|
||||
;;
|
||||
;; The actions for the sign rule push -1 on the stack for a minus sign
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue