From: Alhaitham Al Jabri <jabri.dev@gmail.com>
To: 54448@debbugs.gnu.org
Subject: bug#54448: [PATCH] fix(docs): add missing closing paren to tools/lookup
Date: Fri, 18 Mar 2022 17:53:10 +0400 [thread overview]
Message-ID: <CAD2rCwPn4k_hfE653L6oLpKLk906hAm04+r-UCP+F1NVvXrJ6g@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 146 bytes --]
Hello emacsers,
There is a missing closing parenthesis for the +lookup/documentation
function. This patch fixes it.
Regards,
Alhaitham Al Jabri
[-- Attachment #1.2: Type: text/html, Size: 892 bytes --]
[-- Attachment #2: 0001-fix-docs-add-missing-closing-paren-to-tools-lookup.patch --]
[-- Type: text/x-patch, Size: 992 bytes --]
From 817dfcdfe92e91766cee7c8502324a7ef483e0a5 Mon Sep 17 00:00:00 2001
From: Alhaitham Al Jabri <jabri.dev@gmail.com>
Date: Fri, 18 Mar 2022 17:38:06 +0400
Subject: [PATCH] fix(docs): add missing closing paren to tools/lookup
---
modules/tools/lookup/autoload/lookup.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/modules/tools/lookup/autoload/lookup.el b/modules/tools/lookup/autoload/lookup.el
index 3a727c20..74a29235 100644
--- a/modules/tools/lookup/autoload/lookup.el
+++ b/modules/tools/lookup/autoload/lookup.el
@@ -371,7 +371,7 @@ search otherwise."
;;;###autoload
(defun +lookup/documentation (identifier &optional arg)
- "Show documentation for IDENTIFIER (defaults to symbol at point or selection.
+ "Show documentation for IDENTIFIER (defaults to symbol at point or selection).
First attempts the :documentation handler specified with `set-lookup-handlers!'
for the current mode/buffer (if any), then falls back to the backends in
--
2.35.1
next reply other threads:[~2022-03-18 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 13:53 Alhaitham Al Jabri [this message]
2022-03-19 14:23 ` bug#54448: [PATCH] fix(docs): add missing closing paren to tools/lookup Lars Ingebrigtsen
2022-04-14 14:06 ` Lars Ingebrigtsen
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD2rCwPn4k_hfE653L6oLpKLk906hAm04+r-UCP+F1NVvXrJ6g@mail.gmail.com \
--to=jabri.dev@gmail.com \
--cc=54448@debbugs.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.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).