# I got a really long error stack. I can't see the context and what the actual error

**URL:** <https://discourse.julialang.org/t/i-got-a-really-long-error-stack-i-cant-see-the-context-and-what-the-actual-error/57147>\
**Category:** General Usage\
**Created:** [March 14, 2021, 9:59pm UTC](https://discourse.julialang.org/t/i-got-a-really-long-error-stack-i-cant-see-the-context-and-what-the-actual-error/57147 "2021-03-14T21:59:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![BridgeBot](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bridgebot/32/21491_2.png) [@BridgeBot](https://discourse.julialang.org/u/BridgeBot)\
**Post date:** [March 14, 2021, 9:59pm UTC](https://discourse.julialang.org/t/i-got-a-really-long-error-stack-i-cant-see-the-context-and-what-the-actual-error/57147/1 "2021-03-14T21:59:27Z")

</div>

I got a really long error stack. I can’t see the context and what the actual error was in the REPL. How should I make the REPL “longer” so I can scroll up more to see the error and the context of the error? I’m using VSCode if that matters

Note that the original poster on Slack cannot see your response here on Discourse. Consider _transcribing the appropriate answer back to Slack_, or pinging the poster here on Discourse so they can _follow this thread_.  
[(Original message :slack:)](https://julialang.slack.com/archives/C6A044SQH/p1615758949126800?thread_ts=1615758949.126800&cid=C6A044SQH) [(More Info)](https://github.com/JuliaCommunity/SlackBridge)

---

<div class="post-metadata">

**Author:** ![kimlaberinto](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kimlaberinto/32/21534_2.png) [@kimlaberinto](https://discourse.julialang.org/u/kimlaberinto)\
**Post date:** [March 15, 2021, 12:08am UTC](https://discourse.julialang.org/t/i-got-a-really-long-error-stack-i-cant-see-the-context-and-what-the-actual-error/57147/2 "2021-03-15T00:08:49Z")

</div>

Thank you to @thazhemadam for this solution!

Opening up a separate terminal window, maximizing it, and running Julia there allowed me to see the stacktrace in full and see the context and what the actual error was.