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.

Sign up for GitHub

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

Jump to bottom

Autocorrect "?" to "Debug.Print" #4933

Open
retailcoder opened this issue Apr 24, 2019 · 0 comments
Open

Autocorrect "?" to "Debug.Print" #4933

retailcoder opened this issue Apr 24, 2019 · 0 comments
Labels
difficulty-03-duck Involves more challenging problems and/or developing within and revising the internals API enhancement Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope. feature-autocomplete feature-autocorrect AC issues specific to the "autocorrect" handler up-for-grabs Use this label in conjunction with a difficulty level label, e.g. difficulty-02-ducky

Comments

@retailcoder
Copy link
Member

Linking #4932

The VBE accepts ? and "pretty-prints" it to a Print statement - which works fine when the ? token follows Debug., but makes the statement illegal otherwise.

Let's implement an autocompletion feature that intercepts the keypress when the current logical line of code is empty (barring indentation), and writes Debug.Print instead, placing the caret immediately after the Print token (we can't make it have a trailing whitespace, VBE would eat it).
@retailcoder retailcoder added enhancement Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope. feature-autocomplete feature-autocorrect AC issues specific to the "autocorrect" handler difficulty-02-ducky Resolving these involves the internal API, but with relatively easy problems to solve. up-for-grabs Use this label in conjunction with a difficulty level label, e.g. difficulty-02-ducky labels Apr 24, 2019
@ghost ghost mentioned this issue Apr 25, 2019
Closed
@retailcoder retailcoder added difficulty-03-duck Involves more challenging problems and/or developing within and revising the internals API and removed difficulty-02-ducky Resolving these involves the internal API, but with relatively easy problems to solve. labels Apr 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
difficulty-03-duck Involves more challenging problems and/or developing within and revising the internals API enhancement Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope. feature-autocomplete feature-autocorrect AC issues specific to the "autocorrect" handler up-for-grabs Use this label in conjunction with a difficulty level label, e.g. difficulty-02-ducky
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@retailcoder