Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
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: Mon, 12 Oct 2009 21:23:48 +0200	[thread overview]
Message-ID: <1255375298-sup-2024@peer.zerties.org> (raw)
In-Reply-To: <1255331296-sup-5993@peer.zerties.org>

Excerpts from Christian Dietrich's message of Mo Okt 12 09:11:35 +0200 2009:
> Excerpts from Gaute Hope's message of Fr Okt 09 13:00:19 +0200 2009:
> > Or the thread count isn't aware of the Today mark and still thinks line
> > 2 is thread 2? Don't really know anything about the implementation.
> > 
> > When it happens it doesn't dissapear before I do a M or there is a pull
> > that redraws the screen.. just pressing Ctrl+L or opening/closing a
> > thread doesn't remove it.
> > 
> > As said earlier it only seems to affect the top two threads.
> 
> Hi,
> i also experienced now this Problem, but can't see were this problem
> is located, because i don't touch the internal states of the
> threads. There must be one @thread[curpos] left, which causes this
> Problem.
> 
> greetz didi

Hi,
i think i've fixed the problem now, it was a wrong mapping in
update_text_for_line, now the situation that caused the error before
succeeds. There was a misguiding declaration of @size_widgets in the
init function.

@size_widgets isn't a Hash, mapping line numbers to a size_widget,
it is the same index as in @threads for the specific thread.

greetz didi

PS: please pull :-)
-- 
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


  reply	other threads:[~2009-10-12 19:23 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
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 [this message]
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=1255375298-sup-2024@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