From: Stefan Kangas <stefan@marxist.se>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: [PATCH] Fix typos
Date: Thu, 30 Jun 2022 17:34:19 +0200 [thread overview]
Message-ID: <CADwFkmnAyB6Yfqfe_KiHRGxTxJTjjVY4O5LY9wBF1uQsrrNofg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 25 bytes --]
Please see the attached.
[-- Attachment #2: 0001-Fix-typos.patch --]
[-- Type: text/x-patch, Size: 16145 bytes --]
From 5ecf4e9613993a520844b78880bf57c04f193880 Mon Sep 17 00:00:00 2001
From: Stefan Kangas <stefan@marxist.se>
Date: Thu, 30 Jun 2022 17:33:03 +0200
Subject: [PATCH] ; Fix typos
---
lisp/org-element.el | 14 +++++++-------
lisp/org-fold-core.el | 10 +++++-----
lisp/org-persist.el | 14 +++++++-------
lisp/org-src.el | 2 +-
lisp/org.el | 2 +-
lisp/ox-latex.el | 12 ++++++------
lisp/ox-texinfo.el | 2 +-
testing/lisp/test-org-element.el | 2 +-
testing/lisp/test-ox-publish.el | 2 +-
9 files changed, 30 insertions(+), 30 deletions(-)
diff --git a/lisp/org-element.el b/lisp/org-element.el
index 2a826bdbb..8964770f0 100644
--- a/lisp/org-element.el
+++ b/lisp/org-element.el
@@ -700,7 +700,7 @@ is cleared and contents are removed in the process."
;; DATUM is i.e. a headline, it's property list (`:title'
;; in case of headline) can contain parsed objects. The
;; objects will contain `:parent' property set to the DATUM
- ;; iteself. When copied, these inner `:parent' propery
+ ;; itself. When copied, these inner `:parent' propery
;; values will contain incorrect object decoupled from
;; DATUM. Changes to the DATUM copy will not longer be
;; reflected in the `:parent' properties. So, we need to
@@ -1289,7 +1289,7 @@ parser (e.g. `:end' and :END:). Return value is a plist."
(category (catch 'buffer-category
(unless org-element-org-data-parser--recurse
(org-with-point-at end
- ;; Avoid recusrive calls from
+ ;; Avoid recursive calls from
;; `org-element-at-point-no-context'.
(let ((org-element-org-data-parser--recurse t))
(while (re-search-backward "^[ \t]*#\\+CATEGORY:" (point-min) t)
@@ -6092,7 +6092,7 @@ completing the request."
(log org-element--cache-size 2))
(org-element-cache-reset)
(throw 'org-element--cache-quit t)))
- ;; Done deleting everthing starting before END.
+ ;; Done deleting everything starting before END.
;; DATA-KEY is the first known element after END.
;; Move on to phase 1.
(org-element--cache-log-message
@@ -6664,7 +6664,7 @@ The function returns the new value of `org-element--cache-change-warning'."
;; `org-element--cache-submit-request'). After the edit, we want to
;; look if there was a sensitive removed during edit.
;; FIXME: This is not the most efficient way and we now
- ;; have to delete more elemetns than needed in some
+ ;; have to delete more elements than needed in some
;; cases. A better approach may be storing the warning
;; in the modification request itself.
(let ((org-element--cache-change-warning-before org-element--cache-change-warning)
@@ -6748,7 +6748,7 @@ that range. See `after-change-functions' for more information."
"This variable controls how buffer changes are handled by the cache.
By default (when this variable is nil), cache re-parses modified
-headlines immidiately after modification preserving all the unaffected
+headlines immediately after modification preserving all the unaffected
elements inside the headline.
The default behaviour works best when users types inside Org buffer of
@@ -6870,7 +6870,7 @@ known element in cache (it may start after END)."
;; costly. Instead, we should better re-parse only the
;; headline itself when possible. If a headline is still
;; starting from old :begin position, we do not care that
- ;; its boundaries could have extended to shrinked - we
+ ;; its boundaries could have extended to shrunk - we
;; will re-parent and shift them anyway.
(and (eq 'headline (org-element-type up))
(not org-element--cache-avoid-synchronous-headline-re-parsing)
@@ -7154,7 +7154,7 @@ The element is: %S\n The real element is: %S\n Cache around :begin:\n%S\n%S\n%S"
(cdr (org-element--cache-find (org-element-property :begin real-element) 'both)))
(org-element-cache-reset))))))
-;;; Cache persistance
+;;; Cache persistence
(defun org-element--cache-persist-before-write (container &optional associated)
"Sync cache before saving."
diff --git a/lisp/org-fold-core.el b/lisp/org-fold-core.el
index 68a777de9..212fa09a8 100644
--- a/lisp/org-fold-core.el
+++ b/lisp/org-fold-core.el
@@ -162,7 +162,7 @@
;; functions, it is important to keep in mind that 'invisible text
;; property may have multiple possible values (not just nil and
;; t). Hence, (next-single-char-property-change pos 'invisible) is not
-;; guarantied to return the boundary of invisible/visible text.
+;; guaranteed to return the boundary of invisible/visible text.
;;; Interactive searching inside folded text (via isearch)
@@ -348,7 +348,7 @@ following symbols:
used.
- `merge-folds': Do not distinguish between different types of folding
- specs. This is the most aggressive optimisation with unforseen and
+ specs. This is the most aggressive optimisation with unforeseen and
potentially drastic effects.")
(put 'org-fold-core--optimise-for-huge-buffers 'safe-local-variable 'listp)
@@ -1031,7 +1031,7 @@ TYPE can be either `text-properties' or `overlays'."
(org-fold-core-region (car region) (cdr region) nil)))
(defun org-fold-core--isearch-filter-predicate-text-properties (beg end)
- "Make sure that folded text is searchable when user whant so.
+ "Make sure that folded text is searchable when user want so.
This function is intended to be used as `isearch-filter-predicate'."
(and
;; Check folding specs that cannot be searched
@@ -1096,7 +1096,7 @@ This is a hack, but I do not see a better way around until isearch
gets support of text properties.")
(defun org-fold-core--create-isearch-overlays (beg end)
"Replace text property invisibility spec by overlays between BEG and END.
-All the searcheable folded regions will be changed to use overlays
+All the searchable folded regions will be changed to use overlays
instead of text properties. The created overlays will be stored in
`org-fold-core--isearch-overlays'."
(let ((pos beg))
@@ -1328,7 +1328,7 @@ property, unfold the region if the :fragile function returns non-nil."
;; ---- end of indirect buffer ----
;; If we copy the text under "Headline" from the indirect buffer and
;; insert it under "Another headline" in the base buffer, the inserted
-;; text will be hidden since it's folding text properties are copyed.
+;; text will be hidden since it's folding text properties are copied.
;; Basically, the copied text would have two sets of folding text
;; properties: (1) Properties for base buffer telling that the text is
;; hidden; (2) Properties for the indirect buffer telling that the
diff --git a/lisp/org-persist.el b/lisp/org-persist.el
index c3dfeee87..0658d8401 100644
--- a/lisp/org-persist.el
+++ b/lisp/org-persist.el
@@ -22,7 +22,7 @@
;;; Commentary:
;;
-;; This file implements persistant cache storage across Emacs sessions.
+;; This file implements persistent cache storage across Emacs sessions.
;; Both global and buffer-local data can be stored. This
;; implementation is not meant to be used to store important data -
;; all the caches should be safe to remove at any time.
@@ -77,7 +77,7 @@
;;
;; Each data collection can be associated with a local or remote file,
;; its inode number, or contents hash. The persistent data collection
-;; can later be accessed using either file bufer, file, inode, or
+;; can later be accessed using either file buffer, file, inode, or
;; contents hash.
;;
;; The data collections can be versioned and removed upon expiry.
@@ -256,11 +256,11 @@ They keys are conses of (container . associated).")
"Whether to report read/write time.
When the value is a number, it is a threshold number of seconds. If
-the read/write time of a single variable exceeds the threashold, a
+the read/write time of a single variable exceeds the threshold, a
message is displayed.
When the value is a non-nil non-number, always display the message.
-When the value is nil, never diplay the message.")
+When the value is nil, never display the message.")
;;;; Common functions
@@ -506,7 +506,7 @@ MISC, if non-nil will be appended to the collection."
(defmacro org-persist-read:generic (container reference-data collection)
"Read and return the data stored in CONTAINER.
REFERENCE-DATA is associated with CONTAINER in the persist file.
-COLLECTION is the plist holding data collectin."
+COLLECTION is the plist holding data collection."
`(let* ((c (org-persist--normalize-container ,container))
(read-func-symbol (intern (format "org-persist-read:%s" (car c)))))
(setf ,collection (plist-put ,collection :last-access (float-time)))
@@ -554,7 +554,7 @@ COLLECTION is the plist holding data collectin."
(defmacro org-persist-load:generic (container reference-data collection)
"Load the data stored in CONTAINER for side effects.
REFERENCE-DATA is associated with CONTAINER in the persist file.
-COLLECTION is the plist holding data collectin."
+COLLECTION is the plist holding data collection."
`(let* ((container (org-persist--normalize-container ,container))
(load-func-symbol (intern (format "org-persist-load:%s" (car container)))))
(setf ,collection (plist-put ,collection :last-access (float-time)))
@@ -912,7 +912,7 @@ Do nothing in an indirect buffer."
(delete-directory (file-name-directory ,persist-file)))))
(defun org-persist-gc ()
- "Remove expired or unregisted containers.
+ "Remove expired or unregistered containers.
Also, remove containers associated with non-existing files."
(unless (and org-persist-disable-when-emacs-Q
;; FIXME: This is relying on undocumented fact that
diff --git a/lisp/org-src.el b/lisp/org-src.el
index 970663e6d..26cd533f1 100644
--- a/lisp/org-src.el
+++ b/lisp/org-src.el
@@ -821,7 +821,7 @@ See also `org-src-mode-hook'."
(defun org-src-associate-babel-session (info)
"Associate edit buffer with comint session.
-INFO should be a list simlar in format to the return value of
+INFO should be a list similar in format to the return value of
`org-babel-get-src-block-info'."
(interactive)
(let ((session (cdr (assq :session (nth 2 info)))))
diff --git a/lisp/org.el b/lisp/org.el
index 3bba06d18..dcf951b6f 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -5088,7 +5088,7 @@ This includes angle, plain, and bracket links."
(progn
(add-face-text-property start end face-property)
(add-text-properties start end properties))
- ;; Initialise folding when used ouside org-mode.
+ ;; Initialise folding when used outside org-mode.
(unless (or (derived-mode-p 'org-mode)
(and (org-fold-folding-spec-p 'org-link-description)
(org-fold-folding-spec-p 'org-link)))
diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index 4de89bc78..1aab8ffd5 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -997,7 +997,7 @@ The most comprehensive option can be set with,
which causes source code to be run through
`engrave-faces-latex-buffer', which generates colorings using
Emacs' font-lock information. This requires the Emacs package
-engrave-faces (availible from ELPA), and the LaTeX package
+engrave-faces (available from ELPA), and the LaTeX package
fvextra be installed.
The styling of the engraved result can customised with
@@ -1222,7 +1222,7 @@ as long as it:
In the default value the colors \"EFD\" and \"EfD\" are provided
as they are respectively the foreground and background colours,
just in case they aren't provided by the generated preamble, so
-we can asume they are always set.
+we can assume they are always set.
Within this preamble there are two recognised macro-like placeholders:
@@ -1370,7 +1370,7 @@ which are given by `org-latex-engraved-preamble' and
(t (funcall gen-theme-spec engraved-theme))))
(funcall gen-theme-spec engraved-theme))
(message "Cannot engrave source blocks. Consider installing `engrave-faces'.")
- "% WARNING syntax highlighting unavailible as engrave-faces-latex was missing.\n")
+ "% WARNING syntax highlighting unavailable as engrave-faces-latex was missing.\n")
"\n")
(concat
"\n% Setup for code blocks\n\n"
@@ -1750,7 +1750,7 @@ This is used to choose a separator for constructs like \\verb."
when (not (string-match (regexp-quote (char-to-string c)) s))
return (char-to-string c))))
-(defun org-latex--make-option-string (options &optional seperator)
+(defun org-latex--make-option-string (options &optional separator)
"Return a comma separated string of keywords and values.
OPTIONS is an alist where the key is the options keyword as
a string, and the value a list containing the keyword value, or
@@ -1767,7 +1767,7 @@ nil."
(format "{%s}" value)
value))))))
options
- (or seperator ",")))
+ (or separator ",")))
(defun org-latex--wrap-label (element output info)
"Wrap label associated to ELEMENT around OUTPUT, if appropriate.
@@ -3475,7 +3475,7 @@ to the Verbatim environment or Verb command."
engraved-wrapped
"}")
engraved-wrapped))
- (user-error "Cannot engrave code as `engrave-faces-latex' is unavailible.")))
+ (user-error "Cannot engrave code as `engrave-faces-latex' is unavailable.")))
(cl-defun org-latex-src-block--engraved
(&key src-block info lang caption caption-above-p num-start retain-labels attributes float &allow-other-keys)
diff --git a/lisp/ox-texinfo.el b/lisp/ox-texinfo.el
index a01bb268c..1eec586fd 100644
--- a/lisp/ox-texinfo.el
+++ b/lisp/ox-texinfo.el
@@ -687,7 +687,7 @@ using the `:findex' and `:kindex' properties.
If PLAIN-LIST is a description list whose `:compact' attribute is
non-nil and ITEM has no content but is followed by another item,
then store the `@findex' and `@kindex' values in the next item.
-If the previous item stored its respecive values in this item,
+If the previous item stored its respective values in this item,
then move them to the next item.
INFO is a plist used as a communication channel."
diff --git a/testing/lisp/test-org-element.el b/testing/lisp/test-org-element.el
index 36ddc20d7..89eb2a360 100644
--- a/testing/lisp/test-org-element.el
+++ b/testing/lisp/test-org-element.el
@@ -3769,7 +3769,7 @@ Text
(org-test-with-temp-text "* H\n"
(forward-line)
(or (org-element-at-point) t)))
- ;; Return greater element when ouside contents.
+ ;; Return greater element when outside contents.
(should
(eq 'drawer
(org-test-with-temp-text
diff --git a/testing/lisp/test-ox-publish.el b/testing/lisp/test-ox-publish.el
index 18e6f5ec1..b3b0182f1 100644
--- a/testing/lisp/test-ox-publish.el
+++ b/testing/lisp/test-ox-publish.el
@@ -100,7 +100,7 @@ removed from the final plist."
(cl-remove-if #'file-directory-p
(directory-files dir)))))))
- ;; Check the default trasformation function,
+ ;; Check the default transformation function,
;; org-html-publish-to-html. Because org-test-publish uses
;; org-publish-attachment by default, we must not just override with
;; nil but tell it to remove the :publishing-function from the list.
--
2.30.2
next reply other threads:[~2022-06-30 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 15:34 Stefan Kangas [this message]
2022-07-01 9:45 ` [PATCH] Fix typos Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2019-11-12 13:44 Jonas Bernoulli
2019-11-16 22:36 ` Kyle Meyer
2019-11-16 23:07 ` Kyle Meyer
2012-03-05 0:01 Adam Spiers
2012-03-08 12:51 ` Bastien
2009-05-10 2:34 Nick Dokos
2009-05-10 7:17 ` Carsten Dominik
2009-05-10 13:46 ` Richard Riley
2009-05-10 16:22 ` Nick Dokos
2009-05-10 16:29 ` Nick Dokos
2009-05-10 16:38 ` Richard Riley
2009-05-10 17:22 ` Richard Riley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmnAyB6Yfqfe_KiHRGxTxJTjjVY4O5LY9wBF1uQsrrNofg@mail.gmail.com \
--to=stefan@marxist.se \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).