Pedro Castro

https://github.com/MDeiml/tree-sitter-markdown/issues/33 added support for code chunks. ```lua -- extend markdown parser to rmd files local ft_to_parser = require('nvim-treesitter.parsers').filetype_to_parsername ft_to_parser.rmd = 'markdown' ``` 

The defined was `pandoc#bib#bibs`. The correct is `pandoc#biblio#bibs` ```lua vim.cmd [[ let g:pandoc#biblio#bibs="/home/test/zotero/citations.bib" ]] ```

This feature can make compilation a problem. As `cmp-pandoc` will read an undefined file in the YAML header, this will make the experience of compiling file a problem, as the...

Okay. I think the configuration should be defined in the setup function, something like this: ```lua { bibliography = { global = { --- Enable this feature, default is false...

I added comment as auto in `ecma`: ```sheme (comment) @auto ``` https://user-images.githubusercontent.com/16160544/155643011-1b1c6c9c-ca06-42d9-b62f-e6b9ae7241ba.mp4

> @aspeddro We cannot watch the video because Github says it is corrupt. > > Also, can you explain your previous comment in more detail? When updating the `comment` node...

yes, I always use closed (snippet closes automatically). If you haven't closed the node it's not a `comment`.

Depends on how parser works. Currently the second case is very difficult to map, because the parser does not treat as a special node as `jsdoc` or `partial-document`

Need to resolve pinned dependencies. They are currently specified in `bs-dependencies`. Is `workspaces` in `package.json` equivalent?

> > Need to resolve pinned dependencies. They are currently specified in `bs-dependencies`. Is `workspaces` in `package.json` equivalent? > > See this repository (note the branch) for a minimal example...