On 05/01/2011 09:12 PM, Igor Murzov wrote:
For example, write ls and then go to the start of line, what do you
think $cur and $prev should be set to when completing at that point? I
think both of them should be empty, but then again I also think that in
that case the ls completion should not
On 05/01/2011 05:40 PM, Ville Skyttä wrote:
For example, write ls and then go to the start of line, what do you
think $cur and $prev should be set to when completing at that point? I
think both of them should be empty, but then again I also think that in
that case the ls completion should
For example, write ls and then go to the start of line, what do you
think $cur and $prev should be set to when completing at that point? I
think both of them should be empty, but then again I also think that in
that case the ls completion should not be invoked at all which may be
a bash bug.
This message also appears when you press tab with the cursor at the
beginning of certain commands.
To reproduce this write dpkg move cursor above d and hit tab, this one
is specially annoying since message is repeated until you press ctrl-c
This happens a lot to me when I use reverse-i-search
