-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
An option to disable double quotation auto insertion #4543
Comments
Actually this appears to be buffer language specific. For some languages it includes more matching pair auto insertions than others. E.g. Plain Text appears to have none where as C, C++, JS will insert closing pairs for ' ', " ", ( ), [ ], { }. Which potentially means the relevant setting may already exist given that it is enabled per language in the current build. Any ideas anyone please? Driving me nuts having to constantly fight the unwanted auto insertions :(
|
Thanks for the feature request @iamvoidcoder -I dont think we have a setting for this at the moment, but it makes sense that we would add something like this. |
Release Notes: - Channels: Improved font sizes in chat - Channels: Added a link preview when hovering over links in chat - Channels: Fixed rendering of newlines in chat messages - Added a new setting "use_autoclose" (defaulting to true) that lets you disable autoclose per language. ([#1420](https://github.com/zed-industries/community/issues/1420)) ([#1903](https://github.com/zed-industries/community/issues/1903))
This should be shipped in v0.119.16-pre. |
Check for existing issues
Describe the feature
Can an option to disable double quotation auto insertion be added please? Not many editors have this on by default and if they do there is always a way to turn it off. Don't think there is a way to disable this in the current build. At least I wan't able to find anything relevant in the config file nor any info in discussions.
If applicable, add mockups / screenshots to help present your vision of the feature
No response
The text was updated successfully, but these errors were encountered: