On Sun, Dec 04, 2005 at 04:16:25PM -0600, Richard Laager wrote:
> On Thu, 2005-12-01 at 13:47 -0500, Luke Schierer wrote:
> > ----- Forwarded message from Justin Pryzby <[EMAIL PROTECTED]> -----
> > 
> > Date: Thu, 1 Dec 2005 11:50:04 -0500
> > From: Justin Pryzby <[EMAIL PROTECTED]>
> > To: Debian BTS Submission <[EMAIL PROTECTED]>
> > Subject: Bug#341604: gaim: Please provide a "Next" button for logfile
> >  searching
> > 
> > Package: gaim
> > Version: 1:1.5.0+1.5.1cvs20051015-1
> > Severity: wishlist
> > Tags: upstream
> > 
> > (Bug will be cloned after submission)
> 
> I'm curious what this notation means.
I didn't feel like writing 2 separate bug emails, so I sent one with
both problems (one of which being a "wishlist bug"), and then "cloned"
the single bug to give it a new bug number.  Then I retitled the
clone, and gave it a different severity, also.  Cloned bugs are copied
in entirety to the new bug number at the time of cloning, after that
they are operated on independently.  Its provided for the case that a
given bug report is actually multiple bugs.  Here, I'm just exploiting
my knowledge of the existence of "clone" feature to save myself from
an extra bug header line, or whatever..

> > I have quite large logs sometimes, since I lurk on
> > #aavso:irc.aavso.org.  If I search logs, they are highlighted
> > (correctly, now; I think there used to be a bug though).  But since my
> > log entries are so large, it is difficult to find the highlighted
> > entries.  It would be good if there were a "Next" button, which
> > scrolls to the next instance of the searched word in the current
> > logfile.  (wishlist)
> > 
> > Probably because of the large logsize, I also notice a bug involving
> > poor handling of the logfile search.  I just search #aavso logs for
> > "Troy", and found the instances of that name in the least recent
> > logfile.  Then when I selected the next least recent logfile, there
> > was a delay (~1s) before the log window updated, and then when it did
> > update, the scrollbar started towards the bottom, and then moved
> > towards the top.  This took another ~1s, and I imagine it used lots of
> > CPU time.   (normal severity, I guess, but its mostly just annoying)
> 
> If you could file separate items (an RFE for the first and a bug report
> for the second) at http://sf.net/projects/gaim that'd be great. I know
> the log searching needs work, but I don't know when I'll get to it.
I have done so:

Debian #341607 is now 
http://sourceforge.net/tracker/index.php?func=detail&aid=1373116&group_id=235&atid=100235

Debian #341604 is now 
http://sourceforge.net/tracker/index.php?func=detail&aid=1373109&group_id=235&atid=100235

-- 
Clear skies,
Justin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to