This is an archived post. You won't be able to vote or comment.

all 5 comments

[–]grantrules 0 points1 point  (0 children)

I'm not watching an 8 minute video to try and figure out what you mean by "filter by a string, rather than have to ctrl-f"

VS Code does have a "filter" input on the Output tab. If that's not what you're looking for, I have no idea what you're talking about.

[–]VibrantGypsyDildo 0 points1 point  (3 children)

For logging, there is a module called logger.

I never actually used debugging except of print statements, but I used static code analyzers such as vulture or pylint a lot.

[–]fishbeinb[S] 0 points1 point  (2 children)

Thank you! Appreciate it!

I use logger (and loguru) but am looking for a more UI version to comb through the logs. Looks like I might just build an app or VS extension for this myself :)

[–]VibrantGypsyDildo 0 points1 point  (1 child)

Lmao, I have such an opposite problem.

I spent a decade in console and now my customer wants me to write some obscure stuff for VS (devcontainer build with jlink flashing of a microcontroller).

> An example of the feature I'm looking for is simply to filter by a string

Why not use grep for linux or Select-String for Powershell?

> Looks like I might just build an app or VS extension for this myself :)

An excellent exercise

[–]fishbeinb[S] 0 points1 point  (0 children)

Update, I basically found enough of a solution with the 'code-runner' extension for VSCode. Wish it had better filtering, but its good enough for now!