From: "Rudolf Adamkovič" <[email protected]>
To: [email protected]
Subject: Fix eaten escaping backslash in `org-use-speed-commands' docstring
Date: Sun, 17 Aug 2025 14:17:13 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
The documentation for `org-use-speed-commands' says:
> For example, to activate speed commands when the point is on any
> star at the beginning of the headline, you can do this:
>
> (setq org-use-speed-commands
> (lambda () (and (looking-at org-outline-regexp) (looking-back "^\**"))))
It seems one of the escaping backslash characters in "^\**" was eaten.
If that is correct, please review the attached patch.
Rudy
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Fix-eaten-escaping-backslash-in-the-documentation.patch --]
[-- Type: text/x-patch, Size: 1190 bytes --]
From d538dcadc581b0c43e554c8300b9a60b053ce651 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Rudolf=20Adamkovi=C4=8D?= <[email protected]>
Date: Sun, 17 Aug 2025 14:12:07 +0200
Subject: [PATCH] Fix eaten escaping backslash in the documentation
* lisp/org-keys.el (org-use-speed-commands): Add a missing backslash
to the documentation string of the custom variable. Also, update
`setq' to `setopt' and re-indent for clarity.
---
lisp/org-keys.el | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/lisp/org-keys.el b/lisp/org-keys.el
index f5f005727..98645b0be 100644
--- a/lisp/org-keys.el
+++ b/lisp/org-keys.el
@@ -690,8 +690,10 @@ (defcustom org-use-speed-commands nil
For example, to activate speed commands when the point is on any
star at the beginning of the headline, you can do this:
- (setq org-use-speed-commands
- (lambda () (and (looking-at org-outline-regexp) (looking-back \"^\\**\"))))"
+ (setopt org-use-speed-commands
+ (lambda ()
+ (and (looking-at org-outline-regexp)
+ (looking-back \"^\\\\**\"))))"
:group 'org-structure
:type '(choice
(const :tag "Never" nil)
--
2.39.5 (Apple Git-154)
[-- Attachment #3: Type: text/plain, Size: 221 bytes --]
--
"The introduction of suitable abstractions is our only mental aid to
organize and master complexity."
--- Edsger Wybe Dijkstra, 1930-2002
Rudolf Adamkovič <[email protected]> [he/him]
http://adamkovic.org
next reply other threads:[~2025-08-17 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 12:17 Rudolf Adamkovič [this message]
2025-09-23 12:21 ` Fix eaten escaping backslash in `org-use-speed-commands' docstring Rudolf Adamkovič
2025-09-27 12:44 ` Ihor Radchenko
2025-09-28 14:56 ` Rudolf Adamkovič
2025-09-28 15:00 ` Ihor Radchenko
2025-12-05 16:31 ` Rudolf Adamkovič
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 \
[email protected] \
[email protected] \
[email protected] \
/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.
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).