From: Chunyang Xu <xuchunyang.me@gmail.com>
To: 23289@debbugs.gnu.org
Subject: bug#23289: 25.1.50; Make C-h S ('info-lookup-symbol') support more manuals in emacs-lisp-mode?
Date: Thu, 14 Apr 2016 21:45:09 +0800 [thread overview]
Message-ID: <CAHs_4ikcd+X5psj2n0pGoV4WBZexAowxctp9URRu+Rws9tKV8g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 337 bytes --]
Hi,
In emacs-lisp-mode buffer, C-h S can find symbol from emacs and elisp
info manual, but I find cl-lib is used a lot in many places, so I want
C-h S works for symbols from cl-lib info manual too. There are also
some other emacs related info manuals, I don't know whether it is worth
supporting them as well.
Thanks.
--
Chunyang Xu
[-- Attachment #2: 0001-Add-support-for-cl-lib-symbols-in-C-h-S.patch --]
[-- Type: application/octet-stream, Size: 994 bytes --]
From 8fb79ab1986380e05004db75cef278ac48092347 Mon Sep 17 00:00:00 2001
From: Chunyang Xu <xuchunyang56@gmail.com>
Date: Thu, 14 Apr 2016 21:39:14 +0800
Subject: [PATCH] Add support for cl-lib symbols in C-h S
---
lisp/info-look.el | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lisp/info-look.el b/lisp/info-look.el
index 70d2756..e2fb641 100644
--- a/lisp/info-look.el
+++ b/lisp/info-look.el
@@ -912,7 +912,8 @@ info-complete
;; for things that should go to Function: etc, and those latter
;; are much more important. Perhaps this could change if some
;; sort of fallback match scheme existed.
- ("(elisp)Index" nil "^ -+ .*: " "\\( \\|$\\)")))
+ ("(elisp)Index" nil "^ -+ .*: " "\\( \\|$\\)")
+ ("(cl)Function Index" nil "^ -+ .*: " "\\( \\|$\\)")))
;; docstrings talk about elisp, so have apropos-mode follow emacs-lisp-mode
(info-lookup-maybe-add-help
--
2.8.0
next reply other threads:[~2016-04-14 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 13:45 Chunyang Xu [this message]
2016-04-14 18:05 ` bug#23289: 25.1.50; Make C-h S ('info-lookup-symbol') support more manuals in emacs-lisp-mode? Drew Adams
2016-04-14 18:52 ` John Wiegley
2016-04-16 11:21 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHs_4ikcd+X5psj2n0pGoV4WBZexAowxctp9URRu+Rws9tKV8g@mail.gmail.com \
--to=xuchunyang.me@gmail.com \
--cc=23289@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.