You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,15 @@
1
-
# Blinter — VS Code Batch Linter
1
+
# Blinter — the IDE Batch Linter
2
2
3
-
Blinter integrates the native Blinter executable into Visual Studio Code’s **Run & Debug** workflow so Windows batch files (`.bat`, `.cmd`) get live diagnostics, variable tracking, and actionable quick fixes while you iterate.
3
+
Blinter integrates the native Blinter executable into the IDE's **Run & Debug** workflow so Windows batch files (`.bat`, `.cmd`) get diagnostics and actionable quick fixes while you iterate.
4
4
5
5
## What it does
6
-
- Registers a `blinter-debug` debug type that launches the bundled `blinter.exe` and streams its output into VS Code.
6
+
- Registers a `blinter-debug` debug type that launches the bundled `blinter.exe` and streams its output into the IDE.
7
7
- Parses stdout incrementally to keep the **Problems** panel, hover tooltips, and inline “stupid line” decorations in sync.
8
8
- Exposes a **Blinter Output** view in the Run & Debug sidebar that groups diagnostics (errors, warnings, undefined variables, etc.) and lets you jump straight to problem lines.
9
9
- Provides command-casing quick fixes (configurable) and detailed variable traces for undefined-variable diagnostics.
10
10
11
11
## Requirements
12
-
- Visual Studio Code 1.75.0 or higher (stable or Insiders).
13
-
- Bundled native `blinter.exe` in `bin/` (or `bins/`) inside the extension. The extension does **not** fall back to Python scripts.
12
+
- Visual Studio Code 1.75.0 or higher (stable, Insiders of forks).
14
13
15
14
Important third-party notice
16
15
----------------------------
@@ -26,14 +25,13 @@ is released under the MIT license (see `LICENSE`).
- This VS Code integration and extension scaffolding: Blinter VS Code Extension
28
+
- This the IDE integration and extension scaffolding: Blinter the IDE Extension
30
29
contributors (see repository history / git log)
31
30
32
31
## Quick start
33
-
1. Confirm `bin/blinter.exe` is included alongside the extension (already bundled in the published VSIX).
34
-
2. Open a workspace that contains the batch file you want to lint.
35
-
3. Open the **Run & Debug** view (`Ctrl+Shift+D`) and choose the `Launch Batch (Blinter)` configuration. If prompted, allow VS Code to create a `launch.json` using the snippet below.
36
-
4. Press **Run** (F5). Blinter runs immediately, populating the Problems panel, in-editor highlights, and the Blinter Output view.
32
+
1. Open a workspace that contains the batch file you want to lint.
33
+
2. Open the **Run & Debug** view (`Ctrl+Shift+D`) and choose the `Launch Batch (Blinter)` configuration. If prompted, allow the IDE to create a `launch.json` using the snippet below.
34
+
3. Press **Run** (F5). Blinter runs immediately, populating the Problems panel, in-editor highlights, and the Blinter Output view.
37
35
38
36
Example `launch.json` entry:
39
37
@@ -61,7 +59,6 @@ Example `launch.json` entry:
61
59
62
60
## Output & troubleshooting
63
61
- View → Output → **Blinter** shows the exact command invocation, stdout, and stderr.
64
-
- If `blinter.exe` cannot be located, a warning is raised and the Output channel logs the lookup paths (`bin/` or `bins/`). Copy the executable into one of those folders and rerun.
65
62
- Diagnostics clear automatically when a session ends; start a new Run & Debug session to refresh analysis.
0 commit comments