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

Add option to not overtype on closing pairs #9595

Open
faldor20 opened this issue Feb 11, 2024 · 0 comments · May be fixed by #10878
Open

Add option to not overtype on closing pairs #9595

faldor20 opened this issue Feb 11, 2024 · 0 comments · May be fixed by #10878
Labels
A-helix-term Area: Helix term improvements C-enhancement Category: Improvements E-easy Call for participation: Experience needed to fix: Easy / not much E-good-first-issue Call for participation: Issues suitable for new contributors

Comments

@faldor20
Copy link

I find the behavior of moving the cursor when typing a closing pair ontop op a closing pair rather than adding another one very annoying and almost never what i actually want.
Not being able to add an extra parenthesis in a bunch of closing parentheses without moving all the way through them always catches me off guard.
vscode has a setting called "autoClosingOvertype" which allows you to change this behavior and I propose helix implement something similar.

An example of me pressing "((((()))))" and not getting any closing parens:
test

@faldor20 faldor20 added the C-enhancement Category: Improvements label Feb 11, 2024
@kirawi kirawi added the A-helix-term Area: Helix term improvements label Feb 12, 2024
@kirawi kirawi added E-easy Call for participation: Experience needed to fix: Easy / not much E-good-first-issue Call for participation: Issues suitable for new contributors labels Mar 31, 2024
@verte-zerg verte-zerg linked a pull request Jun 3, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-helix-term Area: Helix term improvements C-enhancement Category: Improvements E-easy Call for participation: Experience needed to fix: Easy / not much E-good-first-issue Call for participation: Issues suitable for new contributors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants