As I'm reading it, he means that if you /set CMDCHARS ':' and then type ':wind', it won't complete to ':window'. This is not true though, I just checked and made sure. On Sun, Sep 02, 2001 at 09:55:38PM -0700, Joseph Carter wrote: [snip] > > 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. [snip] _______________________________________________ List mailing list [EMAIL PROTECTED] http://epicsol.org/mailman/listinfo/list
- [EPIC]Re: Bug#111002: Autocompletion doesn't work when cmdch... Joseph Carter
- [EPIC]Re: Bug#111002: Autocompletion doesn't work when ... j.
- [EPIC]Re: Bug#111002: Autocompletion doesn't work when ... Joseph Carter
- [EPIC]Re: Bug#111002: Autocompletion doesn't work when ... 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
