message
can contain ANSI SGR codes for setting style and color (#9010)cpp11::source_cpp()
on C++ files that have [[cpp11::register]]
decorations (#10387)magrittr
or native R 4.1+) inserted with the “Insert Pipe Operator” keyboard shortcut can now be configured at the project level as well as the global level (#9409)test_that()
calls when the search term starts with “t " (#11082)server-multiple-sessions=0
) (rstudio-pro#1263)+
and ?
, |
, (
, etc do not need to be escaped, and other ERE escape sequences such as \b
, \w
, and \d
are now supported. This matches the behavior of R’s own grep()
function, but note that backslashes do not need to be escaped (as they typically are in R strings) (#9344)_
placeholder as used by the R pipe-bind operator, to be introduced with R 4.2.0. (#10757)dev
chunk option (#9931)#|
will be respected during inline code execution, and will take precedence over conflicting chunk options in the chunk header (#10645). Both YAML tag: value
syntax and valid R expressions will be parsed.HRESULT
error values by logging them as hexadecimal instead of decimal (#10310)message=FALSE
chunk option to suppress messages if the option is set to FALSE (#9436).rs.formatDataColumnDispatch()
iterates through classes of x
(#10073).rs.api.navigateToFile()
is now synchronous and returns document id (#8938)Session > Load Workspace
menu option now explicitly namespaces base::load
if the load
function has been masked in the global environment (#10089)rstudioapi::writeRStudioPreference("data_viewer_max_cell_size", 10L)
(#5100)core::system::userBelongsToGroup
errors under specific sssd configurations (ignore_group_members = true
) (#10829)rstudio-server verify-installation
which caused stale rserver
processes to exist (rstudio-pro#3041)rsandbox
to allow configuring the effective group of the process (#3214)code-server
to 4.4.0 to resolve issue with the latest Python VS Code extension (Pro #3320)code-server
to 4.4.0 to resolve issue with the latest Python VS Code extension (Pro #3320)workbench_jupyterlab
extension. If not globally installed, this will be auto-installed for users on their first JupyterLab session launch (Pro #3429)vscode.extensions.conf
file allowing admins to create a list of VS Code extension that will be pre-installed for all users (Pro #3378)/proxy/<port>
for Jupyter sessions - previously only available if Jupyter Server Proxy was installed (Pro #3339)