Open blairj09 opened 7 months ago
Currently our rules for the pipe shortcut say editorLangId == r
:
I don't know what Quarto currently gives us for editorLangId
, given that it can be R, Python, etc.
Just to link these up, we are tracking some other related issues about Quarto and language features:
Some research ...
I just created a new Quarto document in positron and added an R chunk. With the cursor inside that chunk, I inspected context keys. editorLangId
is 'quarto'
and editorTextFocus
is true
.
https://code.visualstudio.com/api/references/when-clause-contexts#inspect-context-keys-utility
This came up during usability testing with @gadenbuie today, and is a reason he shies away from using Quarto in Positron and/or VS Code.
This came up in our private beta here: https://github.com/posit-dev/positron-beta/discussions/90
Should we do something easy and quick in the short term, like add the pipe shortcut to the RStudio keymap?
After #3523 we have the shortcuts for |>
and <-
provided for Quarto files in the RStudio Keymap but in the long term we would like to support language keyboard shortcuts generally in Quarto chunks.
With an open R file,
cmd+shift+m
will automatically insert R pipe (|>
). However, in an R code chunk within a Quarto document, the same shortcut instead opens thePROBLEMS
panel. The VS Code keyboard shorcuts doc indicates that this is the expected behavior for this keybinding in VS Code: However, it feels like Quarto chunks should prioritize language-specific key bindings. I intentionally left this issue title a bit vague in case there are other bindings that don't function as expected from within quarto chunks.