extra brackets inserted after navigating away from area

[rmflight]

System details:

Positron and OS details:

Positron Version: 2025.07.0 build 170
Code - OSS Version: 1.100.0
Commit: cbe897b
Date: 2025-06-23T03:43:23.429Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 6.12.10-76061203-generic

Interpreter details:

R 4.4.1

Describe the issue:

If I write code involving brackets, matching brackets are inserted just fine and highlighted and colored to match, awesome.

If I navigate away from the code using brackets, and then come back to the code, and type a closing bracket again (pedantic, I know, but that's how I work), extra brackets are inserted.

This does not happen in RStudio (confirmed in RStudio version 2025.05.1+513)

Steps to reproduce the issue:

test_data = rnorm(100, sd = 20)

subset_data = test_data[1:50]

Type the code into a .R file, and then go back to modify the rnorm code to be:

test_data = rnorm(100, sd = 20, mean = 100)

While typing the last bracket (again). An extra bracket will be inserted.

Expected or desired behavior:

The extra bracket isn't inserted.

Were there any error messages in the UI, Output panel, or Developer Tools console?

I don't think so, beyond the extra bracket being highlighted as not having a matching brace.

• Open the relevant Output Channel logs by utilizing this guide: https://positron.posit.co/troubleshooting.html

-->

positron_brackets.mp4

[juliasilge]

Can you explain a little more if you typed the additional ) or if it was automatically added via a completion?

[rmflight]

I used the screencast mode in Positron to show my exact keystrokes, SHIFT+9 and SHIFT+0 are when I type the ( and ) out of habit.

I am typing the additional ) both times, once in the initial writing of the rnorm, and then coming back to it to add more arguments, I type the closing ) again, expecting nothing to get added, because I've used this habit for so many years in RStudio.

In RStudio, it goes, hey, there is already a closing bracket, surely you don't need another one, and just highlights it as I type it. I would have to type another bracket again to get a second bracket, which makes sense in my mind.

In my mind, it's inconsistent behavior, because the first time I do the ), Positron is like, of course there is one here, you typing it is just muscle memory, we won't add another. But the second time when I add more function arguments, it's like well, I guess we need another bracket here.

positron_brackets2.mp4

[juliasilge]

Great, thank you for the details!