Support for RTypst by jalvesaq · Pull Request #575 · R-nvim/R.nvim

jalvesaq · 2026-05-10T00:04:44Z

No description provided.

jalvesaq · 2026-05-10T00:09:35Z

Support for Typst was added to knitr on GitHub on Mar 22, 2026. It's not available in the last released version of knitr.

jalvesaq · 2026-05-10T11:00:09Z

My approach in this pull request was to set the filetype of a .Rtyp file as typst and then enable R.nvim features for the Typst filetype. Would it be better to set a new filetype, Rtyp, and rename ftplugin/typst_rnvim.lua as ftplugin/rtyp_rnvim.lua?

PMassicotte · 2026-05-10T11:00:48Z

    return chunks
 end

+--- Get code chunks from an RTypst (.Rtyp) document by scanning ```{r} and ```  markers.


Can we not use

R.nvim/lua/r/chunk.lua

Lines 97 to 154 in 2d0cd15

local get_rmd_code_chunks = function(bufnr)

local root = require("r.utils").get_root_node()

if not root then return nil end

local query = vim.treesitter.query.parse(

"markdown",

[[

(fenced_code_block)

@fenced_code_block

]]

)

bufnr = bufnr or vim.api.nvim_get_current_buf()

local code_chunks = {}

for id, node, _ in query:iter_captures(root, bufnr, 0, -1) do

local capture_name = query.captures[id]

if capture_name == "fenced_code_block" then

-- Loop through all children of the node and print their type and text

local lang

local info_string_params = {}

local comment_params = {}

local content_text = ""

local start_row, _, end_row, _ = node:range()

for child in node:iter_children() do

if child:type() == "info_string" then

local info_string = vim.treesitter.get_node_text(child, bufnr)

lang, info_string_params = M.parse_info_string_params(info_string)

end

if child:type() == "code_fence_content" then

content_text = vim.treesitter.get_node_text(child, bufnr)

-- Get the parameters specified in the code chunk with #|

comment_params =

M.parse_comment_params(vim.treesitter.get_node_text(node, bufnr))

end

end

-- Create the chunk object with the extracted information

local chunk = Chunk:new(

content_text,

start_row + 1,

end_row,

info_string_params,

comment_params,

lang,

node

)

table.insert(code_chunks, chunk)

end

end

return code_chunks

end

I think rtyps uses the same structure?

I think

local params_str = lines[i]:match("^```{r}$")

Will not capture params in r chunks, like {r echo=FALSE} or {python}

It was easier for me to use regular expressions, but if you could rewrite the function using tree-sitter, it would be great.

PMassicotte · 2026-05-10T11:04:49Z

I think we could just do that in config.lua

vim.treesitter.language.register("markdown", { "quarto", "rmd", "rtyp" })

Then we could just reuse get_rmd_code_chunks + parse_info_string_params + parse_comment_params all. My preliminary understanding is that we already have all the tooling to parse rtyp code chunks.

What do you think?

PMassicotte · 2026-05-10T11:06:10Z

My approach in this pull request was to set the filetype of a .Rtyp file as typst and then enable R.nvim features for the Typst filetype. Would it be better to set a new filetype, Rtyp, and rename ftplugin/typst_rnvim.lua as ftplugin/rtyp_rnvim.lua?

Yes, I think this is the right approach.

jalvesaq · 2026-05-10T11:08:54Z

vim.treesitter.language.register("markdown", { "quarto", "rmd", "rtyp" })

It would not work. Typst is very different from Markdown. It uses = instead of # for titles, and uses # as a prefix for functions in a similar way to LaTeX, which uses \.

jalvesaq · 2026-05-10T11:32:12Z

Yes, I think this is the right approach.

This was my first thought. But then I realized that if the file is a Typst file, we can send the R code to R Console, but we will not be able to process the R code when rendering the PDF because knitr converts a .Rtyp file into a .typ file. If the file extension is already .typ, it would not work because it would overwrite itself.

jalvesaq · 2026-05-10T11:32:33Z

I'll be able to continue working on this only at night...

PMassicotte · 2026-05-10T12:08:20Z

This is what I got so far with TS.

If ok with you, I can push my changes.

PMassicotte · 2026-05-10T12:08:48Z

Note: r_ls should be activated for that filetype.

fix(ftplugin): use pcall for treesitter query set to handle errors refactor(chunk.lua): remove custom RTypst code chunk parsing feat(cursor.lua): add typst support for moving to next code chunk fix(lsp/init.lua): correct iteration over attached_buffers feat(maps.lua): add typst support for RSendChunk and related mappings feat(send.lua): add typst support for sending lines and chunks

PMassicotte · 2026-05-10T12:13:56Z

PS. I have not tested knitting, I do not have the dev version of knitr installed.

PMassicotte · 2026-05-10T12:17:41Z

I will push this, let me know if it works for you, otherwise we can just delete the commit if anything :)

PMassicotte · 2026-05-10T12:46:21Z

I am currently using Markdown parser to get the chunks code, inline params and chunks parameters, The Markdown grammar is resilient enough to work with typst filetype.

I started to implement a typst specific TS extraction code, but we have to do some manually regex job to get the inline parameters in chunks like:

```{r, eval=TRUE}
plot(
  x,
  type = "b",
  main = "Random Normal Values",
  xlab = "Index",
  ylab = "Value"
)
```

What I have done if more a general refactor on how we get the code chunks based on the file type. At the moment, it works with just using Markdown parser, but maybe I could push the current refactor later in another PR.

jalvesaq · 2026-05-10T23:28:00Z

If ok with you, I can push my changes.

Yes, it was OK. I think you have already pushed...

jalvesaq · 2026-05-10T23:47:26Z

I'm getting this message when trying to send a line from a chunk of R code:

Not inside a supported code chunk.

PMassicotte · 2026-05-11T11:03:37Z

I'm getting this message when trying to send a line from a chunk of R code:

Not inside a supported code chunk.

Back to the office, I will have a look.

jalvesaq · 2026-05-11T11:30:20Z

I've just found that the filetype typst does have the lang node if the block is:

```r
x <- rnorm(100)
```

But not if it is:

```{r}
x <- rnorm(100)
```

PMassicotte · 2026-05-11T13:29:34Z

I have some meetings this morning, I think I forgot to push a change yesterday. Will do that soon.

jalvesaq · 2026-05-11T13:36:56Z

There is no hurry, and I will only have spare time next weekend.

Support for RTypst

4a0e644

jalvesaq force-pushed the Rtypst branch from 38eae87 to 4a0e644 Compare May 10, 2026 00:12

PMassicotte reviewed May 10, 2026

View reviewed changes

Enable insertion of chunks with M-r

bf66301

	local get_rmd_code_chunks = function(bufnr)
	local root = require("r.utils").get_root_node()
	if not root then return nil end

	local query = vim.treesitter.query.parse(
	"markdown",
	[[
	(fenced_code_block)
	@fenced_code_block
	]]
	)

	bufnr = bufnr or vim.api.nvim_get_current_buf()
	local code_chunks = {}

	for id, node, _ in query:iter_captures(root, bufnr, 0, -1) do
	local capture_name = query.captures[id]

	if capture_name == "fenced_code_block" then
	-- Loop through all children of the node and print their type and text
	local lang
	local info_string_params = {}
	local comment_params = {}
	local content_text = ""
	local start_row, _, end_row, _ = node:range()

	for child in node:iter_children() do
	if child:type() == "info_string" then
	local info_string = vim.treesitter.get_node_text(child, bufnr)
	lang, info_string_params = M.parse_info_string_params(info_string)
	end

	if child:type() == "code_fence_content" then
	content_text = vim.treesitter.get_node_text(child, bufnr)

	-- Get the parameters specified in the code chunk with #\|
	comment_params =
	M.parse_comment_params(vim.treesitter.get_node_text(node, bufnr))
	end
	end

	-- Create the chunk object with the extracted information
	local chunk = Chunk:new(
	content_text,
	start_row + 1,
	end_row,
	info_string_params,
	comment_params,
	lang,
	node
	)

	table.insert(code_chunks, chunk)
	end
	end

	return code_chunks
	end

Conversation

jalvesaq commented May 10, 2026

Uh oh!

jalvesaq commented May 10, 2026

Uh oh!

jalvesaq commented May 10, 2026

Uh oh!

PMassicotte May 10, 2026

Choose a reason for hiding this comment

Uh oh!

jalvesaq May 10, 2026

Choose a reason for hiding this comment

Uh oh!

PMassicotte commented May 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

PMassicotte commented May 10, 2026

Uh oh!

jalvesaq commented May 10, 2026

Uh oh!

jalvesaq commented May 10, 2026

Uh oh!

jalvesaq commented May 10, 2026

Uh oh!

PMassicotte commented May 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

PMassicotte commented May 10, 2026

Uh oh!

PMassicotte commented May 10, 2026

Uh oh!

PMassicotte commented May 10, 2026

Uh oh!

PMassicotte commented May 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jalvesaq commented May 10, 2026

Uh oh!

jalvesaq commented May 10, 2026

Uh oh!

PMassicotte commented May 11, 2026

Uh oh!

jalvesaq commented May 11, 2026

Uh oh!

PMassicotte commented May 11, 2026

Uh oh!

jalvesaq commented May 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

PMassicotte commented May 10, 2026 •

edited

Loading

PMassicotte commented May 10, 2026 •

edited

Loading

PMassicotte commented May 10, 2026 •

edited

Loading