From: stettberger@dokucode.de (Christian Dietrich)
Subject: [sup-talk] Feature Request: Collecting Lines in Index Mode
Date: Fri, 02 Oct 2009 22:48:24 +0200 [thread overview]
Message-ID: <1254516195-sup-4619@peer.zerties.org> (raw)
In-Reply-To: <1254334371-sup-5145@masanjin.net>
Excerpts from William Morgan's message of Mi Sep 30 20:17:55 +0200 2009:
> Cool idea. I'd like to see how this looks.
>
> > I tried to implement the feature by my self, but the mapping beetween
> > `curpos' and `@threads' in modes/thread-index-mode.rb made this a
> > little bit hard, and i didn't know how to solve this problem without
> > breaking sup. Perhaps you can give me a hint, how this problem with
> > the direct mapping can be solved.
>
> If you look at #regen_text, @text and @lines are the two variables that
> control the display. @text is an array of the GUI elements for each line
> of the display. Right now it's just set to one line for each thread. You
> want to add one additional element at the appropriate position. for each
> date line. GUI elements are represented as arrays of [color, text]
> pairs; you can look at #text_for_thread_at for an example.
>
> Then, you want to make sure that @lines is set correctly. @lines is a
> map (hash) from line number to thread (so that when the user presses a
> key, we know which thread the cursor is resting on).
Thank you, that helped a much. I implemented the feature, it is
available at git://github.com/stettberger/sup-mail.git
branch time_marks, it is one commit ahead of next. It is enabled
with setting the config option ":time_markers_in_index_mode: true"
At runtime it can be toggled via '%' (just randomly choosen by me)
greetz didi
--
No documentation is better than bad documentation
-- Das Ausdrucken dieser Mail wird urheberrechtlich verfolgt.
next prev parent reply other threads:[~2009-10-02 20:48 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 [this message]
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
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=1254516195-sup-4619@peer.zerties.org \
--to=stettberger@dokucode.de \
/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