You can improve the search results by making use of the
simple query language. Here is a list of supported query terms:
index a88f19e28e..7cf7943b7f 100644
@@ -21467,3 +21467,76 @@ (define-public cl-clog
+ (name "sbcl-nkeymaps")
+ (version "0.1.1")
+ (method git-fetch)
+ (uri (git-reference
+ (url "https://github.com/atlas-engineer/nkeymaps")
+ (commit version)))
+ (file-name (git-file-name "nkeymaps" version))
+ (build-system asdf-build-system/sbcl)
+ (list sbcl-alexandria
+ (list sbcl-prove))
+ (home-page "https://github.com/atlas-engineer/nkeymaps")
+ (synopsis "Keymap facility for Common Lisp")
+ (description "Inspired by Emacsy (keymap.scm) which is inspired by Emacs.
+@item Support prefix keys to other keymaps. For instance, if you prefix
+my-mode-map with C-c, then all bindings for my-mode will be accessible after
+@item List all bindings matching a given prefix. (Also known as which-key in
+@item List the bindings associated to a command.
+@item Support multiple inheritance.
+@item Support keycode.
+@item Validate keyspec at compile time.
+@item define-key can set multiple bindings in a single call.
+@item Support multiple scheme to make it easy to switch between, say,
+Emacs-style and VI-style bindings. This orthogonality to keymaps composes
+better than having multiple keymaps: changing scheme applies to the entire
+program, which is easier than looping through all keymaps to change them.
+@item Translate keyspecs as a fallback. For instance if shift-a is not bound,
+@item Behaviour can be customized with global parameters such as
+@item The compose function can merge multiple keymaps together.
+@item Support multiple arguments when that makes sense (e.g. multiple keymaps
+@item Key remapping à-la Emacs.
+@item Typed keymaps, i.e. keymaps where bound values can only be of a given
+type. This is convenient to catch typos, for instance when binding 'FOO
+instead of #'FOO.")
+ (license license:expat)))
+ (sbcl-package->cl-source-package sbcl-nkeymaps))
+ (sbcl-package->ecl-package sbcl-nkeymaps))
index a88f19e28e..30cb605d3b 100644
This issue is archived.
To comment on this conversation send email to email@example.com