@robby Is there a way to remove the behaviour “When typing a closing parenthesis, if the next character is a bracket, just move the cursor over it.”? I still want bracket matching when closing a bracket though.

For example, the current behaviour of automatic parenthesis in comments is incorrect. Try the following: (define (f x) #f ; On the next line, type an open paren, then a close paren. ; ) When typing the closing parenthesis, it jumps to the last parenthesis of the code, thinking that’s already closed.

Currently my workaround is to first type a period, go back one character, then type the closing parenthesis (usually after trying first without the period)—not really ideal.

My current fix is emacs in the terminal + racket mode :smile:

I don’t think that there are any relevant, existing knobs for that.

I have not really taken ownership of that mode (in the sense that I work with it regularly and try to keep it polished up).

So it might possibly be reasonable to consider that behavior a bug?

I do think that the “smarts” in drracket about match parens is basically disabled inside comments

so it may make sense to turn off the automatic matching behavior there.

(I’m not sure how hard it is trying to do a good job inside comments so this may even just be a straight-up bug where the code isn’t doing what its original author intended.)

Sorry I’m not so definitive here.

Where would I find it? In DrRacket code? Or framework?

@laurent.orseau @robby not promising anything just might take a peek

framework I think

racket mode keybindings I think

thanks!

Thank you!

Thank you both. I may take a look too if I find the time.