Has anyone else experianced a bug with LSXCommand when using CommandTabFileComplete? I've found that if I tab complete a files name LS freezes then gets and error and closes down. There isn't a specific error message, just your typical MS message asking you to send the error report to them. If I comment out "CommandTabFileComplete" and CommandNoTabMicroComplete" it works fine.

This is my code for the LSXCommand. Maybe I'm using conflicting features...?


I use a simple script to show the command.

Come to think of it I don't even need to to this as a mzscript :)

I haven't contact the author yet in case it's a well known glitch.

Yes, the exact same thing happened to me. I'm under XP I might add.

Just stepped through the completion code in the debugger, it seems to be an access violation. I'll try to fix it in 1.8.4.

My problem too, has decreased the usablity of LSXcommand a lot.

When can we expect it to get fixed?

Boy I feel stupid, he has already done it.