Chet Ramey <chet.ramey@...> writes: > > On 1/3/15 5:52 PM, Devin Homan wrote: > > >>> Pressing enter issues the "eix readline" command. > >> > >> I can't reproduce this. The potential redisplay issues aside, if you > >> have a file named `readline' in the current directory, or if the > >> completion for `eix' returns `readline' as the only alternative, the > >> word should expand to readlineline (or readline/line if readline is a > >> directory). Completion always takes place at the current cursor > >> position, and the reverse history search leaves the cursor before the > >> character found (`l'). When I replace `eix' with `echo', I see > >> `readlineline' displayed as output. > >> > > > > You seem to have reproduced the bug. I originally posted this on a > > Gentoo forum thinking that this was a Gentoo specific issue. eix was a > > bad example being a distro specific command. But you still got the same > > result with 'echo readline'. The specific command does not matter, all > > that matters is the expansion. If I execute 'echo echo' (to put that > > command into the history buffer) with 'set horizontal-scroll-mode on' > > in .inputrc, and then do a reverse search for that command with 'Ctrl-r > > e' to search for a previously executed command having the letter 'e' and > > then tab complete, I get 'echo echoecho' with the cursor at the second > > 'e'. When I hit enter I get the result for the command 'echo echo'. > > This is what I cannot reproduce. The expansion is correct. If I run > `echo echo' and then type ^Re, whether horizontal scroll mode is enabled > or not, I get the cursor positioned before the `e' in the second echo, > and readline rings the bell to indicate there are no (or more than one) > completions. If I hit return, I see `echo' displayed. > > The `echo readlineline' from the previous example is another example of > the same correct behavior. > > I'm using bash-4.3.30. There was a previous patch (bash-4.3.13/ > readline-6.3.6) that affected horizontal scrolling, but I don't know > what version you're using. Distribution version numbers are not > necessarily related to the upstream patch level. >
I upgraded to readline 6.3 in Gentoo and the problem went away. I was able to reproduce in Raspbian, running readline 6.2, and in Ubuntu for Odroid, running readline 6.3 (I guess judging from the version numbers in the man pages. I could not find deb-version to get the upstream number. dpkg-dev is installed, which should have provided it.). I upgraded Gentoo to readline ebuild 6.3_p8 and then 6.3_p8-r1 and the problem did not occur when testing either version. Not really sure how to get the upstream version number, but according to the Gentoo ebuild guidelines, http://devmanual.gentoo.org/ebuild-writing/variables/, ebuild version numbering should mirror the upstream numbering. _______________________________________________ Bug-readline mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-readline
