# Why does Visual Studio Code not correctly render interpolation arguments in Cmd objects?

**URL:** <https://discourse.julialang.org/t/why-does-visual-studio-code-not-correctly-render-interpolation-arguments-in-cmd-objects/100510>\
**Category:** VS Code\
**Created:** [June 18, 2023, 10:41am UTC](https://discourse.julialang.org/t/why-does-visual-studio-code-not-correctly-render-interpolation-arguments-in-cmd-objects/100510 "2023-06-18T10:41:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ahmed\_Salih](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ahmed_salih/32/206579_2.png) [@Ahmed\_Salih](https://discourse.julialang.org/u/Ahmed_Salih)\
**Post date:** [June 18, 2023, 10:41am UTC](https://discourse.julialang.org/t/why-does-visual-studio-code-not-correctly-render-interpolation-arguments-in-cmd-objects/100510/1 "2023-06-18T10:41:44Z")

</div>

Hello!

Suppose I have:

```julia
a = "Hello";

InterpolatedString = "$a"
InterpolatedCmd = `$a`

```

Then in VS Code it shows up as:

![image](https://global.discourse-cdn.com/julialang/original/3X/8/a/8a6d97c035ea004e3794f11407358981f1c588d6.png)

Shouldn’t this work the same in theory, i.e. be highlighted?

Kind regards

---

<div class="post-metadata">

**Author:** ![mrufsvold](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mrufsvold/32/31600_2.png) [@mrufsvold](https://discourse.julialang.org/u/mrufsvold)\
**Post date:** [June 19, 2023, 8:03am UTC](https://discourse.julialang.org/t/why-does-visual-studio-code-not-correctly-render-interpolation-arguments-in-cmd-objects/100510/2 "2023-06-19T08:03:40Z")

</div>

I think you could put this in as a feature request issue on the extension’s GitHub repo!

---

<div class="post-metadata">

**Author:** ![Ahmed\_Salih](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ahmed_salih/32/206579_2.png) [@Ahmed\_Salih](https://discourse.julialang.org/u/Ahmed_Salih)\
**Post date:** [June 19, 2023, 2:45pm UTC](https://discourse.julialang.org/t/why-does-visual-studio-code-not-correctly-render-interpolation-arguments-in-cmd-objects/100510/3 "2023-06-19T14:45:02Z")

</div>

Okay, thanks, I will do that!

Could you kindly help me figure out which extension it is? I am actually not sure how to check this. I believe I just installed a “Julia” extension in VS Code, perhaps it is just that?

Kind regards

---

<div class="post-metadata">

**Author:** ![CameronBieganek](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cameronbieganek/32/6915_2.png) [@CameronBieganek](https://discourse.julialang.org/u/CameronBieganek)\
**Post date:** [June 19, 2023, 2:49pm UTC](https://discourse.julialang.org/t/why-does-visual-studio-code-not-correctly-render-interpolation-arguments-in-cmd-objects/100510/4 "2023-06-19T14:49:32Z")

</div>

I just opened an issue here:

> <https://github.com/JuliaEditorSupport/atom-language-julia/issues/261>
>
> Could we add a nested TextMate scope for interpolations into commands?
> 
> \<img w…idth="187" alt="image" src="https://github.com/JuliaEditorSupport/atom-language-julia/assets/8310743/d968d6f4-f40b-4dfc-b7c8-709ebc45658a"\>
> 
> \#### String interpolated scope:
> 
> \<img width="578" alt="image" src="https://github.com/JuliaEditorSupport/atom-language-julia/assets/8310743/cb0b95be-90f8-45cf-a1ef-a57695d07122"\>
> 
> \#### No command interpolated scope:
> 
> \<img width="569" alt="image" src="https://github.com/JuliaEditorSupport/atom-language-julia/assets/8310743/42536b4c-78fe-4228-969c-b2179426b725"\>

That repo is where the Julia TextMate grammar lives.

---

<div class="post-metadata">

**Author:** ![Ahmed\_Salih](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ahmed_salih/32/206579_2.png) [@Ahmed\_Salih](https://discourse.julialang.org/u/Ahmed_Salih)\
**Post date:** [June 19, 2023, 5:47pm UTC](https://discourse.julialang.org/t/why-does-visual-studio-code-not-correctly-render-interpolation-arguments-in-cmd-objects/100510/5 "2023-06-19T17:47:37Z")

</div>

Thank you!

I would never have found it, wouldn’t know where to start looking. I just saw someone already implemented the fix for this, mindblowing how fast it actually goes 🙂