From: Christian Dietrich <stettberger@dokucode.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Feature Request: Collecting Lines in Index Mode
Date: Fri, 09 Oct 2009 09:19:30 +0200 [thread overview]
Message-ID: <1255072730-sup-9414@peer.zerties.org> (raw)
In-Reply-To: <1255033079-sup-8556@localdomain>
> And 't' should select the next thread, not the next line. 'a' and 'A'
> too, in fact a time tag should only be selectable manually, using
> Up/Down or 'j'/'k'. Or never if collapsing/expending is possible with a
> mapping (my vote goes to 'E').
Jep thats right, i fixed that. Please pull.
greetz didi
--
No documentation is better than bad documentation
-- Das Ausdrucken dieser Mail wird urheberrechtlich verfolgt.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-09 7:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 18:14 Christian Dietrich
2009-09-30 18:17 ` William Morgan
2009-10-02 20:48 ` Christian Dietrich
2009-10-08 7:05 ` Christian Dietrich
2009-10-08 12:31 ` Christopher Bertels
2009-10-08 12:44 ` Christopher Bertels
2009-10-08 18:28 ` Christian Dietrich
2009-10-08 19:33 ` Christopher Bertels
2009-10-08 19:44 ` Gaute Hope
2009-10-08 20:12 ` Gaute Hope
2009-10-08 20:26 ` Benoît PIERRE
2009-10-09 7:19 ` Christian Dietrich [this message]
2009-10-08 20:50 ` Christian Dietrich
2009-10-09 7:31 ` Gaute Hope
2009-10-09 7:44 ` Christian Dietrich
2009-10-09 9:45 ` Gaute Hope
2009-10-09 10:12 ` Gaute Hope
2009-10-09 10:39 ` Christian Dietrich
2009-10-09 11:00 ` Gaute Hope
2009-10-12 7:11 ` Christian Dietrich
2009-10-12 19:23 ` Christian Dietrich
2009-10-08 20:04 ` Benoît PIERRE
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=1255072730-sup-9414@peer.zerties.org \
--to=stettberger@dokucode.de \
--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