Skip to content
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

Auto-complete should kick in after 0 chars #26

Closed
abrudz opened this issue Jan 11, 2017 · 4 comments · Fixed by #694
Closed

Auto-complete should kick in after 0 chars #26

abrudz opened this issue Jan 11, 2017 · 4 comments · Fixed by #694

Comments

@abrudz
Copy link
Member

abrudz commented Jan 11, 2017

The IDE has a setting for how many characters one needs to write before auto-complete kicks in. Since this setting is not alterable from within RIDE, it should default to 0. It is currently 1.

Example:
In the IDE, set Options>Configure>Auto Complete>Make suggestions after 0 characters.
In the session, type ⎕SE. and wait to see the suggestions.
In RIDE, type ⎕SE.

@jayfoad
Copy link
Contributor

jayfoad commented Dec 4, 2017

I've raised Mantis 15284 to request interpreter support for this.

@johndaintree
Copy link
Contributor

johndaintree commented Dec 4, 2017 via email

@jayfoad
Copy link
Contributor

jayfoad commented Dec 5, 2017

Is it sufficient for RIDE to set that and/or our apl scripts to set it?

@johndaintree That's better than nothing, but it would be much better still if RIDE was in complete control of this, even for interpreters that it did not start. So I think I favour passing the prefix-size value in every GetAutocomplete request.

@e9gille
Copy link
Contributor

e9gille commented May 7, 2018

@johndaintree any news on this? Will it make it into the protocol?

@e9gille e9gille linked a pull request May 1, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants