# Strange error in VS code input

**URL:** <https://discourse.julialang.org/t/strange-error-in-vs-code-input/17961>\
**Category:** VS Code\
**Tags:** error\
**Created:** [November 24, 2018, 11:57pm UTC](https://discourse.julialang.org/t/strange-error-in-vs-code-input/17961 "2018-11-24T23:57:36Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Juan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juan/32/7657_2.png) [@Juan](https://discourse.julialang.org/u/Juan)\
**Post date:** [November 24, 2018, 11:57pm UTC](https://discourse.julialang.org/t/strange-error-in-vs-code-input/17961/1 "2018-11-24T23:57:36Z")

</div>

Hello.

I’ve been using Julia on VS code with language-julia-0.11.0-beta.2.vsix for several days but today it doesn’t work. I don’t know why.

Whatever I try to run on the main editor it adds it a prefix “200~” and generates an error.

For example:  
`using DataFrames, GLM`

produces:

```julia
200~using DataFrames, GLM
ERROR: MethodError: no method matching ~(::Int64, ::Int64)
Closest candidates are:
  ~(::Union{Int128, Int16, Int32, Int64, Int8, UInt128, UInt16, UInt32, UInt64, UInt8}) at int.jl:274
  ~(::Integer) at int.jl:138
Stacktrace:
 [1] top-level scope at none:0

```

Has anyone had the same problem?  
Do you think is a problem wit VS Code, the extension or with Julia?  
running the code directly on the REPL works well.  
I’ve tried reinstalling the extension but the problem is still there.

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [November 25, 2018, 12:08am UTC](https://discourse.julialang.org/t/strange-error-in-vs-code-input/17961/2 "2018-11-25T00:08:49Z")

</div>

Could you open an issue with this over at [GitHub - julia-vscode/julia-vscode: Julia extension for Visual Studio Code](https://github.com/JuliaEditorSupport/julia-vscode)? Thanks!

---

<div class="post-metadata">

**Author:** ![Juan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juan/32/7657_2.png) [@Juan](https://discourse.julialang.org/u/Juan)\
**Post date:** [November 25, 2018, 12:40am UTC](https://discourse.julialang.org/t/strange-error-in-vs-code-input/17961/3 "2018-11-25T00:40:37Z")

</div>

I’ve done it.

I’ve also tried reinstalling a different version of VS Code but the problem persists.

PD: I’ve reinstalled the the extension beta1 and it works but beta2 doesn’t.

---

<div class="post-metadata">

**Author:** ![ArchieCall](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/archiecall/32/206_2.png) [@ArchieCall](https://discourse.julialang.org/u/ArchieCall)\
**Post date:** [November 25, 2018, 12:49am UTC](https://discourse.julialang.org/t/strange-error-in-vs-code-input/17961/4 "2018-11-25T00:49:35Z")

</div>

Select all the code and then press Ctrl-Enter for the Beta2 version to execute the code. For some reason this version does not work with the F5 key to execute the file. It worked OK on the previous version.

---

<div class="post-metadata">

**Author:** ![Juan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juan/32/7657_2.png) [@Juan](https://discourse.julialang.org/u/Juan)\
**Post date:** [November 25, 2018, 1:12am UTC](https://discourse.julialang.org/t/strange-error-in-vs-code-input/17961/5 "2018-11-25T01:12:34Z")

</div>

I wasn’t using the F5 key but Ctrl+Enter.

---

<div class="post-metadata">

**Author:** ![bernhard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bernhard/32/2619_2.png) [@bernhard](https://discourse.julialang.org/u/bernhard)\
**Post date:** [December 3, 2018, 10:15am UTC](https://discourse.julialang.org/t/strange-error-in-vs-code-input/17961/6 "2018-12-03T10:15:19Z")

</div>

Thanks.  
I had the exact same issue.  
Thank you for mentioning that beta 1 works (this is the case for me as well)!  
I also note that, in order to installe the beta release, ‘double clicking’ the vsix did not work for me; instead I had to browse for the file in the extensions menu in VS code.