Package: bc
Version: 1.06.95-9+b3
Severity: minor

Steps to reproduce:

 1. Run bc with no arguments
 2. Type some decimal digits, "3939" say, and do not hit return.
 3. Press ^C to cancel the half-written command
 4. Press ^D to try to quit bc

Expected behaviour: bc silently exits.
Observed behaviour: ^D is ignored.

Hitting return (maybe after typing some other valid expression) gets
out of the weird state.

Note that this is *not* a result of efforts to treat ^D as "delete to
right" since:

 1. Type some decimal digts, "3939" say
 2. Go to start of line with ^A
 3. Press ^D four times, to delete the four digits
 4. Press ^D a fifth time.  bc exits.  This is perhaps justifiable.

So whether ^D exits seems to depend on whether ^C was used, not on
whether the input line is empty.  This doesn't seem sensible.

Weirdly, though, ^C on an empty command does not produce the
^D-does-not-work state.

-- System Information:
Debian Release: 9.9
  APT prefers oldstable-debug
  APT policy: (500, 'oldstable-debug'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-0.bpo.5-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages bc depends on:
ii  libc6         2.24-11+deb9u4
ii  libreadline7  7.0-3
ii  libtinfo5     6.0+20161126-1+deb9u2

bc recommends no packages.

bc suggests no packages.

-- no debconf information

Reply via email to