# Using @debug in Atom console

**URL:** https://discourse.julialang.org/t/using-debug-in-atom-console/15833
**Category:** General Usage
**Tags:** question
**Created:** [October 3, 2018, 4:40pm UTC](https://discourse.julialang.org/t/using-debug-in-atom-console/15833 "2018-10-03T16:40:55Z")
**Posts on this page:** 1
**Showing post:** 2

<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: [October 4, 2018, 12:15pm UTC](https://discourse.julialang.org/t/using-debug-in-atom-console/15833/2 "2018-10-04T12:15:18Z")

</div>

That’s a bug in Atom.jl which should be fixed on `master`. See

> [@Custom logger in Atom?](https://discourse.julialang.org/t/custom-logger-in-atom/15609):
>
> I’d like to customize the response to @info, as in the long quote below. I find this useful for debugging package tests. This works in REPL (Julia 0.7) but not in Atom, where the current logger is wrapped in a JunoProgressLogger (Atom/src/comm.jl:96 or :109). Since loggers are immutable, I believe the only way to do this is to define a new logger. I have tried to detect Atom, and when in Atom setting the new logger like this: Logging.global\_logger(Atom.Progress.JunoProgressLogger(TESTLOGR)) ……

for details.

---

_[View the full topic](https://discourse.julialang.org/t/using-debug-in-atom-console/15833)._