From: Mark Alexander <marka@pobox.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] [PATCH] Fix search-for-next function when using Ruby 1.9
Date: Fri, 17 May 2013 12:51:57 -0400 [thread overview]
Message-ID: <1368809417-sup-3442@x200s> (raw)
[Note: I've submitted a pull request for this fix.]
The use of the 'n' key to search for the next occurrence
of a string stopped working when running sup in Ruby 1.9.
This simple patch fixes that problem.
---
lib/sup/buffer.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/sup/buffer.rb b/lib/sup/buffer.rb
index 444589a..859e0c7 100644
--- a/lib/sup/buffer.rb
+++ b/lib/sup/buffer.rb
@@ -271,7 +271,7 @@ EOS
def handle_input c
if @focus_buf
- if @focus_buf.mode.in_search? && c != CONTINUE_IN_BUFFER_SEARCH_KEY[0]
+ if @focus_buf.mode.in_search? && c != CONTINUE_IN_BUFFER_SEARCH_KEY.ord
@focus_buf.mode.cancel_search!
@focus_buf.mark_dirty
end
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2013-05-17 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 16:51 Mark Alexander [this message]
2013-05-17 16:58 ` Gaute Hope
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=1368809417-sup-3442@x200s \
--to=marka@pobox.com \
--cc=sup-talk@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