# Warning: Terminal not fully functional

**URL:** <https://discourse.julialang.org/t/warning-terminal-not-fully-functional/28579>\
**Category:** Juno\
**Created:** [September 9, 2019, 10:39pm UTC](https://discourse.julialang.org/t/warning-terminal-not-fully-functional/28579 "2019-09-09T22:39:39Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![scone](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@scone](https://discourse.julialang.org/u/scone)\
**Post date:** [September 9, 2019, 10:39pm UTC](https://discourse.julialang.org/t/warning-terminal-not-fully-functional/28579/1 "2019-09-09T22:39:39Z")

</div>

Hi everyone,

I am new to the Discourse and hopefully posted this correctly. I have been dealing with this warning on and off for years while using Juno:

┌ Warning: Terminal not fully functional  
└ @ Base client.jl:353

I usually delete my .atom folder when it happens, reinstall Juno, and live without the problem for a few weeks. Lately, it comes back after I restart Atom. Its surprising no one else seems to have this problem, since I deal with it all the time. I am using fedora, and everything is up to date.

Any ideas would be much appreciated - thanks.

---

<div class="post-metadata">

**Author:** ![baggepinnen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/baggepinnen/32/693_2.png) [@baggepinnen](https://discourse.julialang.org/u/baggepinnen)\
**Post date:** [September 9, 2019, 11:12pm UTC](https://discourse.julialang.org/t/warning-terminal-not-fully-functional/28579/2 "2019-09-09T23:12:00Z")

</div>

I had the same problem back when I was using fedora. For me, it appeared less if I launched atom by typing atom in the terminal rather than launching it from the launcher

---

<div class="post-metadata">

**Author:** ![scone](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@scone](https://discourse.julialang.org/u/scone)\
**Post date:** [September 9, 2019, 11:35pm UTC](https://discourse.julialang.org/t/warning-terminal-not-fully-functional/28579/3 "2019-09-09T23:35:11Z")

</div>

Thanks- that does work! I feel like I should be looking for a permanent fix, but instead I am going to get back to working and feeling less frustrated about it…

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [September 10, 2019, 8:38am UTC](https://discourse.julialang.org/t/warning-terminal-not-fully-functional/28579/4 "2019-09-10T08:38:25Z")

</div>

What’s the output for `ENV["TERM"]` in Juno’s Julia REPL for you?

---

<div class="post-metadata">

**Author:** ![scone](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@scone](https://discourse.julialang.org/u/scone)\
**Post date:** [September 10, 2019, 6:27pm UTC](https://discourse.julialang.org/t/warning-terminal-not-fully-functional/28579/5 "2019-09-10T18:27:11Z")

</div>

When I start it from the terminal and things are working properly, I get: “xterm-256color”.  
When it is not fully functional, I get “dumb”.

---

<div class="post-metadata">

**Author:** ![Bernard\_GODARD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bernard_godard/32/4155_2.png) [@Bernard\_GODARD](https://discourse.julialang.org/u/Bernard_GODARD)\
**Post date:** [September 10, 2019, 10:24pm UTC](https://discourse.julialang.org/t/warning-terminal-not-fully-functional/28579/6 "2019-09-10T22:24:26Z")

</div>

I have the same problem on Oracle Enterprise Linux 7.

It’ s happening almost all the times now except on the first run (when juno installs the atom package).

It’s not just the error message. It is actually not fully functional:

- does not enter package/help mode when pressing ]/?
- workspace pane does not show variables from console session.

After Juno install, it is actually working. It stops working after Atom is restarted.

I will try to add export TERM=xterm-256color to my atom run script.

---

<div class="post-metadata">

**Author:** ![Bernard\_GODARD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bernard_godard/32/4155_2.png) [@Bernard\_GODARD](https://discourse.julialang.org/u/Bernard_GODARD)\
**Post date:** [September 11, 2019, 6:19am UTC](https://discourse.julialang.org/t/warning-terminal-not-fully-functional/28579/7 "2019-09-11T06:19:23Z")

</div>

I can confirm adding:

```julia
 export TERM=xterm-256color 

```

to my atom startup script works.  
Just make sure that the desktop file specifies to run the startup script not directly the binary.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [September 11, 2019, 9:37am UTC](https://discourse.julialang.org/t/warning-terminal-not-fully-functional/28579/8 "2019-09-11T09:37:47Z")

</div>

Ok, this is very weird – Juno is very specifically setting `$TERM = xterm-256color` before starting a REPL. [This commit](https://github.com/JunoLab/atom-julia-client/commit/40e1f13ba2af2c7609e0728d9f0fabd800c292d3) might or might not improve the situation, we’ll see.