-
Notifications
You must be signed in to change notification settings - Fork 24
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
Freezes when typing into a string enclosed by quotes #142
Comments
@jcberquist Hi, just checking if this package is still supported. I've used it since it came out but need to know if I should look for something else. This issue makes it unusable due to freezing/crashing. |
I'm having this same issue. When editing inside any CFML tag on an M1 Macbook Pro I get a beachball and have to force quit the app. I have every extension removed except for Package Control and CFML. If I remove CFML it works fine. |
I am not able to reproduce this locally. I am trying to think of why it would happen when editing inside of a CFML tag. Could you try setting the CFML package setting "cfdocs_enabled" to |
Thanks for such a quick response. I am using the latest ST3 Build 4126 stable. I'm on a 2021 Apple M1 Pro with Monterrey 12.4. It's a company computer so who knows if maybe it's on my end. I tried your suggestion but no joy. Specifically I am inside an ArrayAppend like this. As soon as I type a comma I get the beachball.
I have since finally found an FTP plugin for VSCode that may allow me to switch to VSCode for CF stuff. I've been wanting to do that for a while but this 12+ year old legacy application has a tricky dev/build stack that was easiest with Sublime. I'm happy to do any more troubleshooting if you need it. Thanks! |
Actually, as soon as I type the opening paren in ArrayAppend I get the beachball. |
You could try setting |
I am seeing freezing when typing into a string enclosed by quotes.
Issue is not present when SublimeText is started in safe mode, which doesn't load packages.
First noticed issue after switching to 2022 MacBook Pro with M1.
The text was updated successfully, but these errors were encountered: