[Bug] `vscode-quickmark` does not respect `QUICKMARK_CONFIG` env variable

[singularitti]

Bug Description

The vscode-quickmark extension does not respect the QUICKMARK_CONFIG environment variable, which should allow quickmark to use a configuration file at a custom path. Even though QUICKMARK_CONFIG is set in my shell and visible within VSCode’s process.env, the extension ignores it and fails to pick up my custom config.

Steps to Reproduce

1. Create a custom quickmark.toml file at ~/.config/quickmark.toml.
2. Export the environment variable in my shell:

   export QUICKMARK_CONFIG="$HOME/.config/quickmark.toml"

3. Confirm with echo $QUICKMARK_CONFIG that the path is correct.
4. Open VSCode and confirm process.env.QUICKMARK_CONFIG exists in the dev console.
5. Use the vscode-quickmark extension.

Expected Behavior

The extension should detect and respect the QUICKMARK_CONFIG environment variable and load the configuration from my specified file (~/.config/quickmark.toml).

Actual Behavior

The extension ignores the QUICKMARK_CONFIG environment variable and fails to load my custom config file. It behaves as though no configuration file is present, reverting to defaults.

Environment

• OS: macOS 15.6.1 (24G90)
• QuickMark version: quickmark-cli 1.1.0
• VSCode:

  Version: 1.103.2
  Commit: 6f17636121051a53c88d3e605c491d22af2ba755
  Date: 2025-08-20T16:45:34.255Z
  Electron: 37.2.3
  ElectronBuildId: 12035395
  Chromium: 138.0.7204.100
  Node.js: 22.17.0
  V8: 13.8.500258-electron.0
  OS: Darwin arm64 24.6.0
  

• QuickMark Linter: 0.0.3

Sample Input

Dolor irure nostrud adipisicing exercitation id enim labore fugiat. Esse incididunt officia officia commodo ullamco labore minim. Eu elit ullamco officia velit eu et laborum enim sunt sunt.

Configuration File

[linters.settings.line-length]
line_length = 92

Code of Conduct

• I agree to follow this project's Code of Conduct