diff --git a/README.md b/README.md
index 958a62d..5447f6e 100644
--- a/README.md
+++ b/README.md
@@ -197,6 +197,40 @@ print(factorial(int(Number)))
 
 The Tokay homepage [tokay.dev](https://tokay.dev) provides links to a quick start and documentation. The documentation source code is maintained in a [separate repository](https://github.com/tokay-lang/tokay-docs).
 
+## Debugging
+
+For debugging, there are two methods to use.
+
+### Tracing using the `log`-crate
+
+For Rust standard trace, use the [`env_logger` facilities](https://docs.rs/env_logger/latest/env_logger/). Full trace is only compiled into debug executables, the release version only provides warning level and upwards.
+
+```
+$ RUST_LOG=tokay=debug tokay
+```
+
+Alternatively, tracing can be activated for the `__main__`-program by setting `TOKAY_LOG`. This is used to start tracing when the internal parser has been compiled and executed already, and parsed the actual program. `TOKAY_LOG` can be set to any `RUST_LOG`-compliant format, as it becomes `RUST_LOG` right after.
+
+```
+$ TOKAY_LOG=tokay=debug tokay
+```
+
+### Built-in AST and VM debugger using `TOKAY_DEBUG` and `TOKAY_PARSER_DEBUG`
+
+Set `TOKAY_DEBUG` to a debug level between 1-6. This can also be achieved using `tokay -dddd` where every `d` increments the debug level. Additionally, `TOKAY_INSPECT` can be set to one or a list of parselet name (-prefixes) which should be inspected in VM step-by-step trace (`TOKAY_DEBUG=6`).
+
+| Level | Mode                              |
+| ----- | --------------------------------- |
+| 0     | No debug                          |
+| 1     | Print constructed AST             |
+| 2     | Print final intermediate program  |
+| 3     | Print compiled VM program         |
+| 4     | Print VM execution trace          |
+| 5     | Print VM stack contents           |
+| 6     | VM opcode debugger                |
+
+`TOKAY_PARSER_DEBUG` sets the specific debug level for the parser, which is implemented in Tokay itself and is part of the compiler. Only levels > 2 can be recognized here, as the AST of the parser is built into the code.
+
 ## Logo
 
 The Tokay programming language is named after the [Tokay gecko (Gekko gecko)](https://en.wikipedia.org/wiki/Tokay_gecko) from Asia, shouting out "token" in the night.
diff --git a/src/compiler/compiler.rs b/src/compiler/compiler.rs
index 7a38a7e..d46b68b 100644
--- a/src/compiler/compiler.rs
+++ b/src/compiler/compiler.rs
@@ -6,6 +6,7 @@ use crate::reader::*;
 use crate::value;
 use crate::value::RefValue;
 use crate::vm::*;
+use env_logger;
 use indexmap::{indexset, IndexMap, IndexSet};
 use log;
 use std::cell::RefCell;
@@ -184,6 +185,12 @@ impl Compiler {
             //println!("###\n{:#?}\n###", ast);
         }
 
+        // When TOKAY_LOG is set, set RUST_LOG to the setting *after* internal compilations
+        if let Ok(log) = std::env::var("TOKAY_LOG") {
+            std::env::set_var("RUST_LOG", log.clone());
+            env_logger::init();
+        }
+
         self.compile_from_ast(&ast, None)
     }
 
diff --git a/src/compiler/iml/imlvalue.rs b/src/compiler/iml/imlvalue.rs
index 9e7caae..33d3626 100644
--- a/src/compiler/iml/imlvalue.rs
+++ b/src/compiler/iml/imlvalue.rs
@@ -380,7 +380,7 @@ impl ImlValue {
                     ops.push(Op::LoadFast(*addr))
                 }
             }
-            Self::Instance(instance) => {
+            Self::Instance(_instance) => {
                 todo!();
             }
             _ => unreachable!("{}", self),
diff --git a/src/main.rs b/src/main.rs
index 9c2c5e7..f5b07e3 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -185,7 +185,10 @@ fn repl(opts: &Opts) -> rustyline::Result<()> {
 }
 
 fn main() -> rustyline::Result<()> {
-    env_logger::init();
+    // TOKAY_LOG setting has precedes over RUST_LOG setting.
+    if std::env::var("TOKAY_LOG").is_err() {
+        env_logger::init();
+    }
 
     // Handle command-line arguments from Opts.
     let opts = Opts::parse();