# Different Logging output between Juno Execute and Julia REPL

**URL:** <https://discourse.julialang.org/t/different-logging-output-between-juno-execute-and-julia-repl/30933>\
**Category:** New to Julia\
**Created:** [November 10, 2019, 11:59pm UTC](https://discourse.julialang.org/t/different-logging-output-between-juno-execute-and-julia-repl/30933 "2019-11-10T23:59:05Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)\
**Post date:** [November 12, 2019, 9:38pm UTC](https://discourse.julialang.org/t/different-logging-output-between-juno-execute-and-julia-repl/30933/10 "2019-11-12T21:38:54Z")

</div>

> [@c42f](#):
>
> ![](https://global.discourse-cdn.com/julialang/original/2X/0/040ccd45b75155a12f4a17dd9018baa78841919b.jpeg) pfitzseb:
> 
> > just stop (ab-)using the logging system for progress bars
> 
> I hope you don’t have to do this by the way 🙂 I still think it can be a great solution for unifying progress bars in a way which allows packages to emit progress messages without any dependencies

Just to think out side the box (or maybe I’m just late to the discussion), but what is the advantage of using logging system to record progress events? In principle, there can be a simple package that sets up a global `Channel` or a hook registry so that we can have various frontends and backends. This way, we don’t need to route anything because it’s an API completely separate from normal logging.

---

_[View the full topic](https://discourse.julialang.org/t/different-logging-output-between-juno-execute-and-julia-repl/30933)._