-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Something odd with backslashes and completion #173
Comments
I think you need to configure a parser to suit your needs.
|
Please reopen if needed |
Yes, sure I can work round the issue. |
I think the problem is in your completer. |
Hello. Can confirm this behavior It caused by two things:
Second one is caused by default |
Ok, so just haven't read this issue properly. I think I should create new one for the second part, because this issue is not about it... |
I can confirm this. I think a new issue would be better to track that. As parsing |
This should have been affected by #245 |
I'm trying to write a simple jline completer that will help me enter a filename, so it will take the current line as a path, list the files, and so on. I can write the completer I want, I'm just getting very odd behaviour with backslashes.
I'm running on Windows, and actually doing this through karaf (I haven't actually been able to create a simple standalone example of running jline of ANY kind, a simple working hello world example would be really good).
If I type "c:/" (note forward slash) at the prompt and tab, my completer gets called, and I correctly get a displayed list of all files in c:. If however I type "c:" instead (backslash) then I get a listing, but what I've typed has been replaced by "cc:". All completion then fails. If I type in, say, "c:\work" (a valid path), my completer gets called, but nothing is displayed. So backslashes appear to make it all go wrong.
My completer is:
I'm setting lineReader.setOpt(LineReader.Option.DISABLE_EVENT_EXPANSION); in an attempt to avoid backslashes being replaced.
The text was updated successfully, but these errors were encountered: