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

Overly aggressive paredit in REPL window #255

Closed
lspector opened this issue Jul 14, 2019 · 2 comments
Closed

Overly aggressive paredit in REPL window #255

lspector opened this issue Jul 14, 2019 · 2 comments
Labels
paredit Paredit and structural editing

Comments

@lspector
Copy link

lspector commented Jul 14, 2019

If I type [1 2 3] in the REPL window and then decide that I want it to be (shuffle [1 2 3]) then if I click at the beginning and type ( then it adds ) right after it automatically, which is the sort of thing I've come to expect both in Calva and in other environments... but unlike when this happens in other contexts there appears to be no way to delete the ) no matter what I do.

I know that I'm an outlier in not personally liking any automatic typing of closing brackets ever, and also in not wanting to learn/use Paredit commands (I prefer ordinary typing), and I don't expect the behavior of Calva to change in response to my preferences! But the middle ground adopted in Calva editor windows -- adding closing brackets but letting me delete them -- works well enough for me, and presumably also for others.

So my request is that the REPL window acts like the editor windows in this respect.

@PEZ
Copy link
Collaborator

PEZ commented Jul 16, 2019

Thanks. It is a pity with the separate behaviours between the prompt and the editors. I'll see what I can do about it. Meanwhile, you might find that alt+backspace is your friend at times. It force-deletes stuff, bypassing paredit's demands for structure integrity.

@lspector
Copy link
Author

lspector commented Jul 16, 2019

Ahh, thanks -- alt+backspace is indeed now my friend. I hope I don't forget about it, and agree that consistent behaviors would be desirable in the long run (because, alas, I will probably forget 😊).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
paredit Paredit and structural editing
Projects
None yet
Development

No branches or pull requests

3 participants