On Sun, Sep 02, 2001 at 09:55:38PM -0700, Joseph Carter wrote: > > Autocompletion of commands only works if you start with a /, regardless of the > > value of cmdchar. I guess the autocompletion code doesn't honour this and uses > > a hardcoded default. > > You do mean that /wind expands to /window if it matches nothing else (an > internal feature of the client) instead of some script feature, correct? No, I don't mean that. I mean that if cmdchar is '!' for example, and I type "!ser<TAB>", it expands to "!ser: ", as if I typed a nickname, while if I type "\ser<TAB>", it shows me two alternatives, "SERVER" or "SERVLIST". -- Met vriendelijke groet / with kind regards, Guus Sliepen <[EMAIL PROTECTED]>
- [EPIC]Re: Bug#111002: Autocompletion doesn't work when cmdch... Joseph Carter
- Re: [EPIC]Re: Bug#111002: Autocompletion doesn't work w... j.
- [EPIC]Re: Bug#111002: Autocompletion doesn't work when ... Joseph Carter
- Re: [EPIC]Re: Bug#111002: Autocompletion doesn't work w... Guus Sliepen
- Re: [EPIC]Re: Bug#111002: Autocompletion doesn't work w... Kurt Roeckx
- Re: [EPIC]Re: Bug#111002: Autocompletion doesn't work w... Kurt Roeckx
- Re: [EPIC]Re: Bug#111002: Autocompletion doesn't work w... Joseph Carter
- Re: [EPIC]Re: Bug#111002: Autocompletion doesn't work w... Joseph Carter
- Re: [EPIC]Re: Bug#111002: Autocompletion doesn't work w... Guus Sliepen
- Re: [EPIC]Re: Bug#111002: Autocompletion doesn't work w... Jeremy Nelson
- Re: [EPIC]Re: Bug#111002: Autocompletion doesn't work w... Guus Sliepen
PGP signature