From: Hamish <dmishd@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] [BRANCH] Ctrl-W behaviour
Date: Mon, 21 Feb 2011 01:29:20 +0000 [thread overview]
Message-ID: <1298251460-sup-4333@whisper> (raw)
I use Ctrl-W when deleting labels from a thread, and it's been a minor
annoyance that this is slightly broken - when there is a space before
the cursor, Ctrl-W will just delete the space, and you need to press
Ctrl-W a second time to delete the word aswell. This is not how I'm used
to it working in vim or on the command line.
So I've now had a go at fixing it, in the branch called ctrl_w - just
one commit so far, and it took quite a bit of farting around to get this
far. I'll review it when it's not the early hours of the morning and
merge it into next at that point.
Please have a go and see if you can get any strange behaviour - I had
some strange behaviour with single-letter labels, but I seem to have
fixed that ...
Hamish Downer
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2011-02-21 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 1:29 Hamish [this message]
2011-02-22 17:01 ` Hamish
2011-02-23 13:19 ` Alvaro Herrera
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=1298251460-sup-4333@whisper \
--to=dmishd@gmail.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