From: John Anthony <john@jo.hnanthony.com>
To: 15599@debbugs.gnu.org
Subject: bug#15599: [PATCH] Inferior Lisp Mode Menu
Date: Sat, 12 Oct 2013 18:21:00 +0100 [thread overview]
Message-ID: <20131012172100.GA738@jo.hnanthony.com> (raw)
In-Reply-To: <20131012170846.GA688@jo.hnanthony.com>
[-- Attachment #1: Type: text/plain, Size: 179 bytes --]
Oh, I'm terribly sorry. I used a quasiquote when a quote would have
done. This is probably the worst thing that has ever happened and I am
suitably embarrassed.
--
John Anthony
[-- Attachment #2: inf-lisp-mode-menu2.patch --]
[-- Type: text/x-diff, Size: 954 bytes --]
diff --git a/lisp/progmodes/inf-lisp.el b/lisp/progmodes/inf-lisp.el
index d73e948..eda7fda 100644
--- a/lisp/progmodes/inf-lisp.el
+++ b/lisp/progmodes/inf-lisp.el
@@ -91,6 +91,19 @@ mode. Default is whitespace followed by 0 or 1 single-letter colon-keyword
(define-key map "\C-c\C-v" 'lisp-show-variable-documentation)
map))
+(easy-menu-define
+ inferior-lisp-menu
+ inferior-lisp-mode-map
+ "Inferior Lisp Menu"
+ '("Inf-Lisp"
+ ["Eval Last Sexp" lisp-eval-last-sexp t]
+ ["Load File" lisp-load-file t]
+ ["Compile File" lisp-compile-file t]
+ ["Show Arglist" lisp-show-arglist t]
+ ["Describe Sym" lisp-describe-sym t]
+ ["Show Fucntion Doc" lisp-show-function-documentation t]
+ ["Show Variable Doc" lisp-show-variable-documentation t]))
+
;;; These commands augment Lisp mode, so you can process Lisp code in
;;; the source files.
(define-key lisp-mode-map "\M-\C-x" 'lisp-eval-defun) ; Gnu convention
next prev parent reply other threads:[~2013-10-12 17:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 17:08 bug#15599: [PATCH] Inferior Lisp Mode Menu John Anthony
2013-10-12 17:21 ` John Anthony [this message]
2013-10-12 19:16 ` Stefan Monnier
2013-10-19 2:48 ` Glenn Morris
2013-10-22 0:56 ` John Anthony
2013-10-22 14:23 ` Stefan Monnier
2013-10-24 7:25 ` Glenn Morris
2013-10-23 21:47 ` John Anthony
2013-10-24 7:20 ` Glenn Morris
2013-10-24 14:05 ` John Anthony
2013-10-25 2:36 ` Glenn Morris
2013-10-24 14:33 ` Stefan Monnier
2013-10-24 15:00 ` Drew Adams
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=20131012172100.GA738@jo.hnanthony.com \
--to=john@jo.hnanthony.com \
--cc=15599@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.