Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [PATCH 1/3] make mode keymap easily accessible to hooks
Date: Sun, 24 Jan 2010 19:09:31 -0800	[thread overview]
Message-ID: <1264388973-5804-1-git-send-email-rlane@club.cc.cmu.edu> (raw)

---
 lib/sup/mode.rb |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/lib/sup/mode.rb b/lib/sup/mode.rb
index c8ad0cc..b9e0698 100644
--- a/lib/sup/mode.rb
+++ b/lib/sup/mode.rb
@@ -10,6 +10,10 @@ class Mode
     @@keymaps[self] = keymap
   end
 
+  def self.keymap
+    @@keymaps[self] || register_keymap
+  end
+
   def initialize
     @buffer = nil
   end
-- 
1.6.3.3

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


             reply	other threads:[~2010-01-25  3:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25  3:09 Rich Lane [this message]
2010-01-25  3:09 ` [sup-devel] [PATCH 2/3] add keymap rebinding support Rich Lane
2010-01-25  3:09   ` [sup-devel] [PATCH 3/3] keybindings hook Rich Lane
2010-02-27  7:34     ` Rich Lane

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=1264388973-5804-1-git-send-email-rlane@club.cc.cmu.edu \
    --to=rlane@club.cc.cmu.edu \
    --cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox