# Terminal not fully functional

**URL:** <https://discourse.julialang.org/t/terminal-not-fully-functional/121737>\
**Category:** New to Julia\
**Created:** [October 25, 2024, 7:46am UTC](https://discourse.julialang.org/t/terminal-not-fully-functional/121737 "2024-10-25T07:46:24Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [October 28, 2024, 2:53am UTC](https://discourse.julialang.org/t/terminal-not-fully-functional/121737/21 "2024-10-28T02:53:10Z")

</div>

> [@Warning: Terminal not fully functional with Julia 1.0.5 on Windows](https://discourse.julialang.org/t/warning-terminal-not-fully-functional-with-julia-1-0-5-on-windows/67522/25):
>
> If I do `set TERM=` and then press enter. This sets the variable to an empty string. I clear the `TERM` environmental variable and then Julia functions as normal, allowing me to access the pkg and help modes as normal.

Did you look at: [Environment variables](https://www3.ntu.edu.sg/home/ehchua/programming/howto/Environment_Variables.html) ?

And which version of Windows do you have?

The output of:

```julia
julia> get(ENV, "TERM", "")
"dumb"

```

should be empty, and not “dumb”.

Someone else wrote:

> So remove the TERM system variable from Windows 10 environment variables settings fix this issue without any further updates.
> 
> Now, type echo $TERM shown the default value: xterm-256color works for everything…

---

_[View the full topic](https://discourse.julialang.org/t/terminal-not-fully-functional/121737)._
