#106033 dselect: successful search "/<foo>" blinks screen, simulates bouncing return key

Package:
dselect
Source:
dpkg
Description:
Debian package management front-end
Submitter:
Jeff Sheinberg
Date:
2005-07-18 03:26:56 UTC
Severity:
minor
#106033#5
Date:
2001-07-20 19:10:27 UTC
From:
To:
Package: dpkg
Version: 1.9.16
Severity: normal

Hi,

After a successful search using the "/" command, dselect does the
following,

    1. re-draws the screen.

    2. after a short delay, ~400ms, the screen is cleared and then
       re-drawn.

    3. sometimes, dselect behaves as if the original search
       command were followed by two carriage returns, rather than
       just the single carriage return entered.

Comments on the above,

    1. cool!

    2. redundant, and highly annoying behavior by dselect.

    3. thus popping me into the main dselect menu, this behavior
       by dselect is enough to drive me psycho!  No, my keyboard
       is not broken, I never get multiple carriage returns in
       xterm (where dselect is being run from), emacs, etc.

Thanks,
#106033#10
Date:
2001-07-20 23:09:26 UTC
From:
To:
severity 106033 minor
thanks


Previously Jeff Sheinberg wrote:

Known problem, not a high-priority thing though.

I've never heard of this before, unless you can give me a reliably
way to reproduce this I'm afraid I can't fix it.

Wichert.
#106033#17
Date:
2001-07-20 23:19:01 UTC
From:
To:
Processing commands for control@bugs.debian.org:
Bug#106033: dpkg: dselect: successful search "/<foo>" blinks screen, simulates bouncing return key
Severity set to `minor'.
Stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)
#106033#22
Date:
2001-07-20 23:31:30 UTC
From:
To:
Wichert Akkerman writes:
 > Previously Jeff Sheinberg wrote:
 > >     2. after a short delay, ~400ms, the screen is cleared and then
 > >        re-drawn.
 >
 > Known problem, not a high-priority thing though.

This should be real easy to fix since the "\" command already does
the right thing.

 >
 > >     3. sometimes, dselect behaves as if the original search
 > >        command were followed by two carriage returns, rather than
 > >        just the single carriage return entered.
 >
 > I've never heard of this before, unless you can give me a reliably
 > way to reproduce this I'm afraid I can't fix it.
 >

I have a tendency to "rest" on the return key, especially when I
become cranky.  Also, I am in the bad habit of using the keyboard
auto-repeat feature, and in X I have the delay set to 250ms, where
I do most of my work, so this combination is probably the cause of
the double return.  So, lets consider this part of the bug report
to be closed due to "user error".

Thanks,