From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] new branch: keybindings
Date: Tue, 08 Feb 2011 09:07:31 +0100 [thread overview]
Message-ID: <1297152370-sup-4647@qwerzila> (raw)
In-Reply-To: <1297152028-sup-5512@qwerzila>
Excerpts from Gaute Hope's message of 2011-02-08 09:01:44 +0100:
> Excerpts from Rich Lane's message of 2011-01-28 05:26:38 +0100:
> Could it be that this broke continue buffer search key 'n' ?
>
> lib/sup/buffer.rb:171
>
> This doesn't work for me anymore, could anyone confirm that?
Ah - I just noticed that I have to move down one line before I can hit
'n' to search for the next occurrence. I don't think this was the
original, or desired, behaviour?
- Gaute
next prev parent reply other threads:[~2011-02-08 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 4:26 Rich Lane
2011-02-08 8:01 ` Gaute Hope
2011-02-08 8:07 ` Gaute Hope [this message]
2011-02-13 18:05 ` 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=1297152370-sup-4647@qwerzila \
--to=eg@gaute.vetsj.com \
--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