Verbose Mode
This guide explains how to use DeepLint's verbose mode to get more detailed information about command execution.
Overview
DeepLint provides a verbose mode that outputs additional information during command execution. This can be helpful for:
Debugging issues with DeepLint
Understanding what DeepLint is doing behind the scenes
Getting more context about the analysis process
Troubleshooting configuration problems
Basic Usage
To enable verbose mode, use the --verbose
flag or its shorthand -v
:
deeplint --verbose
This will run the default command with verbose output enabled.
You can also use verbose mode with specific commands:
deeplint init --verbose
deeplint help --verbose
What Verbose Mode Shows
When verbose mode is enabled, DeepLint will output additional information about:
Configuration loading and validation
Command execution steps
Context building process
File scanning and analysis
Git operations
Command-specific operations
For example, when running the default command with verbose mode:
deeplint --verbose
You'll see additional output like:
π Context building configuration:
π - Repository root: /path/to/your/project
π - Context type: light
π - Include unstaged changes: false
π - Max tokens: 8000
π - Include dependencies: false
π - Include structure: true
π Starting context building process...
π Context building process completed.
π Context building statistics:
π - Total files: 42
π - Changed files: 3
π - Related files: 5
π - Total tokens: 2500
π - Build time: 120ms
Combining with Other Flags
Verbose mode can be combined with other flags:
deeplint --verbose --unstaged
This will run the default command with verbose output and include unstaged changes in the analysis.
Examples
Here are some examples of using verbose mode with different commands:
deeplint --verbose
Runs the default command with verbose output, showing detailed information about the context building process.
When to Use Verbose Mode
Verbose mode is particularly useful in the following scenarios:
Troubleshooting: When DeepLint isn't behaving as expected, verbose mode can help identify where the issue is occurring.
Learning: If you're new to DeepLint, verbose mode can help you understand what's happening behind the scenes.
Complex Projects: In large projects with many files, verbose mode can provide insights into how DeepLint is analyzing your code.
Custom Configurations: If you've customized your DeepLint configuration, verbose mode can help verify that your settings are being applied correctly.
Next Steps
Now that you understand how to use verbose mode, you can:
Try running DeepLint with verbose mode to see the additional information it provides
Use verbose mode to troubleshoot any issues you encounter
Learn more about DeepLint's configuration options
For more information about DeepLint's commands, see the Help Command guide.
Last updated