# How to have the suppressed bytes shown using ASTInterpreter?

**URL:** <https://discourse.julialang.org/t/how-to-have-the-suppressed-bytes-shown-using-astinterpreter/2033>\
**Category:** New to Julia\
**Created:** [February 10, 2017, 9:11pm UTC](https://discourse.julialang.org/t/how-to-have-the-suppressed-bytes-shown-using-astinterpreter/2033 "2017-02-10T21:11:56Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![chobbes](https://avatars.discourse-cdn.com/v4/letter/c/848f3c/32.png) [@chobbes](https://discourse.julialang.org/u/chobbes)\
**Post date:** [February 10, 2017, 9:11pm UTC](https://discourse.julialang.org/t/how-to-have-the-suppressed-bytes-shown-using-astinterpreter/2033/1 "2017-02-10T21:11:56Z")

</div>

I’m using ASTInterpreter to step through a piece of code by a collaborator. However, since some of the keywords are really lengthy, they’re not shown but suppressed. I’m wondering if there is a way to have the words shown, irrespective of the length of the contents.

`About to run: (size)(<suppressed 93 bytes of output>,1)`

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ihnorton/32/26_2.png) [@ihnorton](https://discourse.julialang.org/u/ihnorton)\
**Post date:** [February 11, 2017, 5:17am UTC](https://discourse.julialang.org/t/how-to-have-the-suppressed-bytes-shown-using-astinterpreter/2033/2 "2017-02-11T05:17:57Z")

</div>

Tweak the length threshold or revert this PR (locally):

[https://github.com/Keno/ASTInterpreter.jl/pull/45](https://github.com/Keno/ASTInterpreter.jl/pull/45)

(you’ll understand why the change was made very quickly if you work with any moderate-sized array or step into IO code)

---

<div class="post-metadata">

**Author:** ![chobbes](https://avatars.discourse-cdn.com/v4/letter/c/848f3c/32.png) [@chobbes](https://discourse.julialang.org/u/chobbes)\
**Post date:** [February 11, 2017, 12:08pm UTC](https://discourse.julialang.org/t/how-to-have-the-suppressed-bytes-shown-using-astinterpreter/2033/3 "2017-02-11T12:08:16Z")

</div>

Thanks for the comments. Could you please elaborate a little more on how to tweak the length threshold? I’m not quite inclined to locally revert that particular commit. Thanks!

---

<div class="post-metadata">

**Author:** ![tim.holy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tim.holy/32/52_2.png) [@tim.holy](https://discourse.julialang.org/u/tim.holy)\
**Post date:** [February 11, 2017, 4:27pm UTC](https://discourse.julialang.org/t/how-to-have-the-suppressed-bytes-shown-using-astinterpreter/2033/4 "2017-02-11T16:27:57Z")

</div>

If you click on that link, it takes you to the pull request. Then click on “files changed” and you can see which lines of code were added (green). Look at the code, and from there you can probably figure out what you need to change.

---

<div class="post-metadata">

**Author:** ![chobbes](https://avatars.discourse-cdn.com/v4/letter/c/848f3c/32.png) [@chobbes](https://discourse.julialang.org/u/chobbes)\
**Post date:** [February 11, 2017, 5:21pm UTC](https://discourse.julialang.org/t/how-to-have-the-suppressed-bytes-shown-using-astinterpreter/2033/5 "2017-02-11T17:21:10Z")

</div>

Thank you very much for pointing that out. I see it now. Just curious - isn’t it more convenient if ASTInterpreter users are allowed to set this number at REPL, instead of changing this line locally?

---

<div class="post-metadata">

**Author:** ![tim.holy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tim.holy/32/52_2.png) [@tim.holy](https://discourse.julialang.org/u/tim.holy)\
**Post date:** [February 11, 2017, 9:33pm UTC](https://discourse.julialang.org/t/how-to-have-the-suppressed-bytes-shown-using-astinterpreter/2033/6 "2017-02-11T21:33:26Z")

</div>

The easiest approach is to not modify it at all. At the prompt, type the ` key, and then inspect the variable at the interactive prompt by typing it at the (now green) prompt. Or if it’s the output of a function call, just re-run the function.

If that’s still not good enough, one could talk about further customization, but that might be best done on GitHub.

---

<div class="post-metadata">

**Author:** ![chobbes](https://avatars.discourse-cdn.com/v4/letter/c/848f3c/32.png) [@chobbes](https://discourse.julialang.org/u/chobbes)\
**Post date:** [February 11, 2017, 9:38pm UTC](https://discourse.julialang.org/t/how-to-have-the-suppressed-bytes-shown-using-astinterpreter/2033/7 "2017-02-11T21:38:11Z")

</div>

Printing the variables by using ``` is a solution. But it requires quite a lot of extra typing, which significantly slows down the debugging. I wish more customization can be introduced to the future version of Julia debuggers.

Thanks for the comments!!!