On 18/06/12 08:46 PM, Stefan Lippers-Hollmann wrote: > I'm lowering the severity to minor, because in my opinion this > doesn't impose a significant impact on wpa_cli's usability.
Sure. As a workaround, I'll just press and hold the enter key periodically. A bit ugly, but serves the same function. > This is caused by switching wpa_cli to the new (since 1.0~) > internal readline replacement, which might not have all the bells > and whistles GNU readline has to offer, yet(?). I saw that in the changelog and figured that was it. > You can confirm this by rebuilding wpa with this patch: Thanks. If it really gets irritating, I might, but I'll give the readline replacement a chance first ... > So far this seems to be the only side effect Well, perhaps not the only one (will file a separate bug about that though :) > of switching to WPA_CLI_EDIT (personally I didn't even notice that > yet), and abandoning readline usage is wanted for licensing reasons > (especially looking at the wpa 2.x branch and readline6/ GPL-3). Ah. All very reasonable. > With a little luck, this feature may get added to future upstream > versions, as there seems to be some rudimentary ctrl-L handling > already. In which case we'd consider backporting it to wpa - > although likely not for wheezy. Sure. Looking forward to that. > As we want/ need to avoid depending on GNU readline, I may tag this > bug as wontfix for the time being. Although I certainly hope that > wpa_cli's internal readline implementation gains feature parity > with GNU readline in the externally visible regards. Would be nice. Now to go file that bug I mentioned ... Ben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
