Ark LSP in .qmd documents in positron #10194
-
DescriptionIt seems line in .qmd documents in positron the autocomplete features (which I think are part of Ark?) aren't available in r chunks in .qmd documents? They are in notebooks and .r documents obviously. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 2 replies
-
Sorry. I don't understand what you are saying or asking here or the exact context. |
Beta Was this translation helpful? Give feedback.
-
.qmd support is Positron is brought up by Quarto VSCODE extension that lives in https://github.com/quarto-dev/quarto Do you have it installed ? it does not come installed by default in Positron. |
Beta Was this translation helpful? Give feedback.
-
I am saying there seems to be some kind of clash between the Quarto VSCODE extensions (i.e. the help pane etc) , and the LSP build into positron such that when I am in quarto chunks and in visual model the code auto complete suggestions provided by positron don't always work, and tab results in what I perceive as unintended behaviour. The entire line is indented when I tab which the cursor between the quotes in read.csv2(file=""), which I'd expect to suggest files in the corrent folder (what the behaviour in source mode and in .r documents) |
Beta Was this translation helpful? Give feedback.
-
To me the tab behaviour in source and visual mode seems inconsistent, but I guess to an extend (certainly outside the code blocks) the tab having word processor like behaviour makes a lot of sense? |
Beta Was this translation helpful? Give feedback.
-
I believe you may be running into a couple of these issues:
If you have additional context to add to those issues @MichelNivard we would welcome that! |
Beta Was this translation helpful? Give feedback.
-
Hi @juliasilge i think you are right, i had searched but didn’t find a prior issue. I’ll close this issue and see if I have any specific experience not covered in the other two issues. |
Beta Was this translation helpful? Give feedback.
I believe you may be running into a couple of these issues:
If you have additional context to add to those issues @MichelNivard we would welcome that!