From: Morgan Smith <Morgan.J.Smith@outlook.com>
To: emacs-orgmode@gnu.org
Cc: Morgan Smith <Morgan.J.Smith@outlook.com>
Subject: [PATCH] ; fix typos
Date: Wed, 19 Jun 2024 11:20:04 -0400 [thread overview]
Message-ID: <CH3PR84MB3424433EB71EA954A813F717C5CF2@CH3PR84MB3424.NAMPRD84.PROD.OUTLOOK.COM> (raw)
* doc/org-manual.org: Add missing '~'.
* lisp/org-element-ast.el (org-element-deferred): Fix typo in docstring.
* lisp/org-element.el (org-element-archive-tag,
org-element-drawer-re-nogroup, org-element--cache-log-message): Fix
typos in docstring.
(org-element--current-element, org-element--cache-find,
org-element-cache-map): Fix typos in comments.
---
doc/org-manual.org | 2 +-
lisp/org-element-ast.el | 2 +-
lisp/org-element.el | 13 ++++++-------
3 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 96c90eaab..9bc58de60 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -23190,7 +23190,7 @@ * Footnotes
=(diary-date 12 1 2005)= or =(diary-date 1 12 2005)= or =(diary-date
2005 12 1)=, depending on the settings. This has been the source of
much confusion. Org mode users can resort to special versions of
-these functions, namely ~org-date~, ~org-anniversary~, ~org-cyclic, and
+these functions, namely ~org-date~, ~org-anniversary~, ~org-cyclic~, and
~org-block~. These work just like the corresponding ~diary-~
functions, but with stable ISO order of arguments (year, month, day)
wherever applicable, independent of the value of
diff --git a/lisp/org-element-ast.el b/lisp/org-element-ast.el
index fba6b37e6..2c767e1ad 100644
--- a/lisp/org-element-ast.el
+++ b/lisp/org-element-ast.el
@@ -270,7 +270,7 @@ Return value is the containing property name, as a keyword, or nil."
"Dynamically computed value.
The value can be obtained by calling FUNCTION with containing syntax
-node as first argument and ARGS list as remainting arguments.
+node as first argument and ARGS list as remaining arguments.
If the function throws `:org-element-deferred-retry' signal, assume
that the syntax node has been modified by side effect and retry
diff --git a/lisp/org-element.el b/lisp/org-element.el
index 191bb5698..811d32276 100644
--- a/lisp/org-element.el
+++ b/lisp/org-element.el
@@ -110,7 +110,7 @@
;; to current setup.
(defconst org-element-archive-tag "ARCHIVE"
- "Tag marking a substree as archived.")
+ "Tag marking a subtree as archived.")
(defconst org-element-citation-key-re
(rx "@" (group (one-or-more (any word "-.:?!`'/*@+|(){}<>&_^$#%~"))))
@@ -181,8 +181,7 @@ Drawer's name is located in match group 1.")
(rx line-start (0+ (any ?\s ?\t))
":" (1+ (any ?- ?_ word)) ":"
(0+ (any ?\s ?\t)) line-end)
- "Regexp matching opening or closing line of a drawer.
-Drawer's name is located in match group 1.")
+ "Regexp matching opening or closing line of a drawer.")
(defconst org-element-dynamic-block-open-re
(rx line-start (0+ (any ?\s ?\t))
@@ -4679,7 +4678,7 @@ element it has to parse."
;;
;; In general, the checks below should be as efficient as
;; possible, especially early in the `cond' form. (The
- ;; early checks will contribute to al subsequent parsers as
+ ;; early checks will contribute to all subsequent parsers as
;; well).
(cond
;; Item.
@@ -5956,7 +5955,7 @@ better to remove the commands advised in such a way from this list.")
(defmacro org-element--cache-log-message (format-string &rest args)
"Add a new log message for org-element-cache.
-FORMAT-STRING and ARGS are the same arguments as in `foramt'."
+FORMAT-STRING and ARGS are the same arguments as in `format'."
`(when (or org-element--cache-diagnostics
(eq org-element--cache-self-verify 'backtrace))
(let* ((format-string (concat (format "org-element-cache diagnostics(%s): "
@@ -6226,7 +6225,7 @@ the cache."
;; children starting at the same pos.
(not (org-element-type-p hashed '(section org-data table))))
hashed
- ;; No appriate HASHED. Search the cache.
+ ;; No appropriate HASHED. Search the cache.
(while node
(let* ((element (avl-tree--node-data node))
(begin (org-element-begin element)))
@@ -8323,7 +8322,7 @@ the cache."
limit-count))
(cache-walk-abort))
;; Make sure that we have a cached
- ;; element at the new STAR.
+ ;; element at the new START.
(when start (element-match-at-point)))
;; Check if the buffer or cache has been modified.
(unless (org-with-base-buffer nil
--
2.45.1
next reply other threads:[~2024-06-19 15:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 15:20 Morgan Smith [this message]
2024-06-19 15:36 ` [PATCH] ; fix typos Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2022-06-30 15:34 [PATCH] Fix typos Stefan Kangas
2022-07-01 9:45 ` Ihor Radchenko
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=CH3PR84MB3424433EB71EA954A813F717C5CF2@CH3PR84MB3424.NAMPRD84.PROD.OUTLOOK.COM \
--to=morgan.j.smith@outlook.com \
--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).