The manual is a work in progress. Please add to it with complete, tested instructions wherever you can.  

Images in the manual may differ from what you see in your version of Huggle.

Debugging huggleEdit

When things go wrong and huggle doesn't behave as it should, there is a fairly large toolkit that can be used to debug what is wrong.

Verbosity of programEdit

Huggle can be started in so-called "debug mode" in this mode, interface contains few buttons and menus that are normally hidden and display much more technical information that normally aren't visible. You can start huggle in verbose mode by passing it -v parameter where amount of v's is level of verbosity (for example, -vv is verbosity level 2).

You can also switch running huggle into debug mode (it can't be switched back, though) by opening help → about and moving the mouse cursor over the name of Petrb and Addshore. Doing so (approx. 10 times) will pop up a message box.

System logEdit

Huggle produces a system log, this log contains much more information when in debug mode. You can see the system log in a widget on bottom (in default layout setup). Or you can have huggle write it to a file. It can be continuously written to a file when you start Huggle using parameter --syslog <name of file>.

If you are reporting a bug or problem with huggle, this system log can be useful for developers in order to figure out what is wrong.

Traffic dumpEdit

One of the most effective ways to diagnose the issues. Enabling traffic dump using parameter --qd will generate an output file that contains raw traffic sent by huggle and received from web servers. This file will be called querydump.dat and it will be located in a working directory from which Huggle was started. On Windows, this path can be defined in shortcut properties. This file can be very huge even in very short time. It may contain sensitive information and it's recommended to examine it before sending to anyone untrusted.