5
54
Fork
You've already forked blue
4

Introduce a --debug flag #265

Open
opened 2026年03月20日 19:31:37 +01:00 by pastor · 1 comment

The debug flag should probably set the logging level to debug set the profile to debug (we probably need to decide what this means) and set the backtraces to show more stack frames.

We should also hide unnecessary stack frames on the backtraces. As we discussed this is quite verbose for the user. In my recent testings implementing the org stencil, the verbosity made it uncomfortable to navigate and find the information I was interested in. Of course Emacs is quite powerful and I can easily navigate long backtraces but I expect many terminal users to struggle with so much verbosity.

The debug flag should probably set the logging level to `debug` set the profile to `debug` (we probably need to decide what this means) and set the backtraces to show more stack frames. We should also hide unnecessary stack frames on the backtraces. As we discussed this is quite verbose for the user. In my recent testings implementing the [org stencil](https://codeberg.org/lapislazuli/blue/src/branch/user-manual/blue/stencils/org.scm), the verbosity made it uncomfortable to navigate and find the information I was interested in. Of course Emacs is quite powerful and I can easily navigate long backtraces but I expect many terminal users to struggle with so much verbosity.
pastor added this to the alpha milestone 2026年03月20日 19:31:37 +01:00
Author
Owner
Copy link

After discussion we've decided that it would be better to introduce the concept of log levels.

We've envisioned the following levels:

  • user (default): print backtraces up to user code.
  • blue: print backtraces up to BLUE code.
  • pluggings: print backtraces up to plugging code.
  • guile: print backtraces up to system libraries, eg: guile and guile libraries.

The flag will have the following aspect: --debug=blue.

Additionally, this can be controlled through a BLUE preference.

After discussion we've decided that it would be better to introduce the concept of log levels. We've envisioned the following levels: - user (default): print backtraces up to user code. - blue: print backtraces up to BLUE code. - pluggings: print backtraces up to plugging code. - guile: print backtraces up to system libraries, eg: guile and guile libraries. The flag will have the following aspect: `--debug=blue`. Additionally, this can be controlled through a BLUE preference.
Sign in to join this conversation.
No Branch/Tag specified
main
pipeline-operators
documentation
shadow-fields
instance-walker
blue-shell
promote-serializers-to-metacommands
pre-alpha
Labels
Clear labels
bug
Something is not working
contribution welcome
Contributions are very welcome, get started here
discussion
duplicate
This issue or pull request already exists
enhancement
New feature
good first issue
Interested in contributing? Get started here.
help wanted
Need some help
invalid
Something is wrong
optimization
question
More information is needed
upstream
Related to an upstream repository, already reported there
bug
Something is not working
contribution welcome
Contributions are very welcome, get started here
duplicate
This issue or pull request already exists
enhancement
New feature
good first issue
Interested in contributing? Get started here.
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
upstream
Related to an upstream repository, already reported there
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lapislazuli/blue#265
Reference in a new issue
lapislazuli/blue
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?