From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [BRANCH] Ctrl-W behaviour
Date: Wed, 23 Feb 2011 10:19:15 -0300 [thread overview]
Message-ID: <1298467110-sup-4536@alvh.no-ip.org> (raw)
In-Reply-To: <1298393768-sup-7839@whisper>
Excerpts from Hamish's message of mar feb 22 14:01:29 -0300 2011:
> Excerpts from Hamish's message of Mon Feb 21 01:29:20 +0000 2011:
> > 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.
>
> I've now merged this into next. I forgot to put the patches in email
> last night, so I've put the branch diff at the end of this email.
I've been using this and it works great. I was annoyed by the original
behavior too.
--
Álvaro Herrera <alvherre@alvh.no-ip.org>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2011-02-23 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 1:29 Hamish
2011-02-22 17:01 ` Hamish
2011-02-23 13:19 ` Alvaro Herrera [this message]
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=1298467110-sup-4536@alvh.no-ip.org \
--to=alvherre@alvh.no-ip.org \
--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