02. PATH not found — tooling anyway
File types, CLI discovery, VS Code + LSP, logging flags, and where the reference manuals hide.
PATH not found — tooling anyway
You have a binary. Now you need a workflow that does not devolve into grep archaeology every time the compiler disagrees with your mental model.
This chapter folds the old “tooling and editors” material into something you can actually use: what files exist, how discovery works, how the extension talks to the same project graph as the CLI, and where to read when you want every flag documented.
What you will find here
Section titled “What you will find here”| Section | Topic |
|---|---|
| File types and discovery | .bd, .proj, Project.proj, Workspace.proj. |
| VS Code and LSP | Extension, language ids, bundled vs local LSP. |
| CLI tour | Subcommands you will touch in week one. |
| Logging and debug flags | Progress, verbosity, and not drowning in noise. |
| Reference deep dives | Pointers to CLI/LSP/project reference trees. |
By the end of this chapter
Section titled “By the end of this chapter”- Know which file extensions mean what.
- Configure editor support for
.bdand.proj. - Know where CLI vs LSP vs analysis share the same manifest model.