Feature Request: Auto-print after breakpoint
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.5k
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
Having to constantly press the p command is getting tiresome. I would like to suggest a couple of features:
1) automatically execute a number of commands after a breakpoint. Commands could be semicolon separated. So like this:
```
_ = "breakpoint; p myInt; n; p myInt; c"
```
Which would cause the "myInt" variable to be printed, the next line to be executed, the "myInt" variable to be printed again, and then the continue command.
2) Set a mode so that the value of all local variables are automatically printed after a breakpoint, or during stepping.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the breakpoint, p, n, and c commands are handled. Define how semicolon-separated commands and automatic local-variable printing should behave, then verify both requested modes at breakpoints and during stepping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100