# Feedback please! More detailed documentation for Graphical Debugger

**URL:** <https://swi-prolog.discourse.group/t/feedback-please-more-detailed-documentation-for-graphical-debugger/3246>\
**Category:** Help!\
**Created:** [November 10, 2020, 3:07am UTC](https://swi-prolog.discourse.group/t/feedback-please-more-detailed-documentation-for-graphical-debugger/3246 "2020-11-10T03:07:23Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ericzinda](https://avatars.discourse-cdn.com/v4/letter/e/b3f665/32.png) [@ericzinda](https://swi-prolog.discourse.group/u/ericzinda)\
**Post date:** [November 13, 2020, 1:15am UTC](https://swi-prolog.discourse.group/t/feedback-please-more-detailed-documentation-for-graphical-debugger/3246/4 "2020-11-13T01:15:42Z")

</div>

> [@jan](#):
>
> the command line editor is not (always) GNU readline based. In fact, the default one is based on BSD libedit for two reasons (1) license compatibility and (2).

I actually got that from the [existing docs](https://www.swi-prolog.org/gtrace.html) 🙂 . Removed now.

> [@jan](#):
>
> This library allows using ssh to get a new thread with a Prolog toplevel to interact with the program

I’ll add a note about this.

> [@jan](#):
>
> Otherwise the only problem I found is the dark purple explanation text on the black background

Here’s another try in green. Let me know if this doesn’t fix it:

 ![](https://global.discourse-cdn.com/free1/uploads/swiprolog/original/2X/9/933ba9e0110803ffda52b3b01ad80fc50c39bdf4.jpeg)

> [@jan](#):
>
> That is quite an important tool as it allows debugging on errors whether or not they are caught.

OK, I’ll post when I get this section written up. Thanks!

---

_[View the full topic](https://swi-prolog.discourse.group/t/feedback-please-more-detailed-documentation-for-graphical-debugger/3246)._