expose context for cell language

[isabelizimm]

Notes

This will update the exposed language depending on what language chunk the user's cursor is in. It will expose the language extension (eg. py, r, jl) used to run the chunk.

The language at position does not immediately change when a cursor is placed, you have to delete or type something non-whitespace for the cell language to update. I still think this is the right place; BUT there is an alternative location where we would get feedback immediately with the language of the virtual doc, rather than the chunk. For reticulate documents, that means you'll never have Python exposed, only R.

Trying it out

I've been testing by creating a file something like:

---
title: new title
editor: source
---


```{r}

```


```{python}

```

and adding these keybindings via Command Palette -> Preferences: Open Keyboard Shortcuts (JSON):

// Place your key bindings in this file to override the defaults
[
    {
        "key": "cmd+shift+a",
        "command": "type",
        "args": { "text": "Hello PYTHON" },
        "when": "quarto.cellLang == 'py'"
      },
      {"key": "cmd+shift+a",
      "command": "type",
      "args": { "text": "Hello RLANG" },
      "when": "quarto.cellLang == 'r'"
    },
    {"key": "cmd+shift+a",
    "command": "type",
    "args": { "text": "Hello QUARTO" },
    "when": "quarto.cellLang == ''"
  },
]

Then I'll go into each chunk, start typing, then do command+shift+a.

[cscheid]

(@isabelizimm I hope you don't mind I took the liberty to edit your post so the triple ticks render fine! The trick is to use more ticks on the outside than on the inside, ```` in this case.)

[isabelizimm]

The trick is to use more ticks on the outside than on the inside, ```` in this case.

TIL!!! Thank you so much, that looks much better 😺

[juliasilge]

Did you try using the ids element? It would be nice if we had the same string here that we can use with editorLangId, i.e. "python" and not "py".

[juliasilge]

If so, it would be nice to make this quarto.cellLangId as well.

[juliasilge]

I installed the .vsix and see the new context key, using "Developer: Inspect Context Keys":

I think it's very unlikely that one of the language keyboard shortcuts would be the first non-whitespace thing you type in a code cell, based on all the examples we currently have. I would rather risk that than have us provide R language shortcuts in a Python cell for knitr/reticulate .qmd files. Happy to re-evaluate if folks find it surprising!