bin/39604: /bin/ksh + TAB-expand $VAR = misplaced cursor

[Ephaeton%gmx.net@localhost]

>Number:         39604
>Category:       bin
>Synopsis:       /bin/ksh + TAB-expand $VAR = misplaced cursor
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Sep 22 02:25:00 +0000 2008
>Originator:     Martin S. Weber
>Release:        4.99.72 / i386
>Organization:
>Environment:
NetBSD agamemnon.entropie.local 4.99.72 NetBSD 4.99.72 (AGAMEMNON) #4: Sat Sep 
20 20:45:58 EDT 2008  
root%agamemnon.entropie.local@localhost:/home/netbsd/obj/sys/arch/i386/compile/AGAMEMNON
 i386
>Description:
This is /bin/ksh from a current build a few days ago. ^V says:
 $ PD KSH v5.2.14 99/07/13.2

When you have ksh expand a variable (in emacs mode I might add, didn't try in 
vi mode), the cursor is placed one place too far right afterwards. Like:
$ a=a/path/to
$ ls $a/now<TAB>
-> $ ls a/path/to/now <CURSOR HERE>
>How-To-Repeat:
(in /bin/ksh)
mkdir -p /tmp/netbsd/rocks
n=/tmp/netbsd
ls $n/ro<NOW HIT TAB>
# output will expand $n to /tmp/netbsd,
# append the /ro you've typed in addition,
# but will end up the cursor one column too far right so
# you cannot hit TAB, say, another time to get the fragment
# /ro expanded to /rocks
>Fix:
Unknown. Maybe some beer helps?