Feature request: Allow shortcut modification so that after executing last statement in quarto cell (ctrl+enter), don't jump fence and go to next cell

In positron, in a qmd document, in quarto source mode, in an R chunk, when executing individual statements in a cell via a shortcut (e.g., ctrl+enter), after execution the cursor goes to the next statement. If you come to the last statement in the cell it will jump the fence at the end of the cell and go to the next cell.

For my workflow, going to the next statement is great when you're in the cell. But skipping to the next cell when at end can disrupt my workflow. Often I'm working within the cell, refining code, and running it statement by statement. The next cell could be 50 lines later (e.g., lots of text between one R code chunk and the next). If I find myself 50 lines later than I just was, usually I have to find my way back to where I was before.

It would be great to have the ability to modify the keyboard shortcut so that the advance-to-next-statement behavior occurs unless you're at the last executable line in the current cell. If you're at the last executable line, it will just stay there.

Maybe there's a way to do this now, but I tried quite a bit. I couldn't figure it out and none of the chatbots I tried could, either.

I realize this is an esoteric use case but would be a nice-to-have feature. Thanks for considering it.

Start by tracing how Ctrl+Enter is handled in Positron for a .qmd document in Quarto source mode, especially within an R chunk. Determine where advancing to the next statement or crossing the cell fence is selected; done means the behavior can be configured to remain on the last executable line while preserving advancement within the cell.