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

[Bug]: Intellisense does not recognise e.g., "begin" as a valid completion #61

Open
2 of 4 tasks
steinhh opened this issue Jan 15, 2025 · 1 comment
Open
2 of 4 tasks
Labels
type: bug Something isn't working

Comments

@steinhh
Copy link

steinhh commented Jan 15, 2025

Current Behavior

When typing (at least some) control words such as "begin", intellisense does not recognize/suggest the word as a valid completion even after typing out the whole word:

Screenshot 2025-01-15 at 15 01 05

This it does with in-scope variable names:
Screenshot 2025-01-15 at 14 52 49

This may not seem like a big deal, "just don't use the intellisense suggestion", but: in other languages the combination of intellisense + copilot is so good that I've had to bind accept-suggestion to ENTER, in order to prevent repetitive strain injury from all the tabbing to accept suggestions. What happens to me now is that I type "begin" and hit enter, resulting in the acceptance of a gibberish suggestion...

Expected Behavior

Intellisense completion should be aware of control words, suggesting those as the default when the entire word has been typed in.

GitHub Repo

No response

Steps to Reproduce

See "current behaviour"

Failure Logs

No response

Operating System

  • macOS (Intel x86_64)
  • macOS (ARM64)
  • Linux
  • Windows

IDL Version

N/A

Additional Information

@martinwiesmann

@steinhh steinhh added the type: bug Something isn't working label Jan 15, 2025
@steinhh
Copy link
Author

steinhh commented Jan 15, 2025

Hmm... it seems if I hit backspace/delete to delete the n at the end of begin, then type it back, there's no suggestion any more and I can safely hit enter, escaping the need to hit escape (another RSI risk...), yay! Also, if in the middle of writing "begin" hit arrow-right (taking me to the start of the next line) and then arrow-left back to the same position as before, when I continue typing the top suggestion becomes "Begin-end statement" which is ok. Not exactly a fix, but a data point :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant