No description
* feat: add healthcheck Problem: users had no way to diagnose why completions were missing or incomplete beyond checking for the ghostty executable. Solution: add a :checkhealth module that verifies blink.cmp is installed, ghostty is on PATH, +show-config --docs produces output, and the bash completion file exists for enum values. * fix: revert blanket diagnostics.disable and selene comments Problem: .luarc.json blanket-disabled four diagnostic categories project-wide, and selene inline directives were added to suppress warnings on io.open monkey-patching in tests. Solution: revert .luarc.json to match main and remove selene comments. * refactor: reuse main module's bash completion path resolution in healthcheck Problem: health.lua duplicated the entire bash completion file resolution chain (exepath -> realpath -> prefix match -> path construction) from the main module, risking drift if the logic changes. Solution: extract M.bash_completion_path() from parse_enums() and call it from both parse_enums and the healthcheck. |
||
|---|---|---|
| .github | ||
| lua | ||
| spec | ||
| .busted | ||
| .editorconfig | ||
| .gitignore | ||
| .luarc.json | ||
| .pre-commit-config.yaml | ||
| .prettierignore | ||
| .prettierrc | ||
| blink-cmp-ghostty-scm-1.rockspec | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE | ||
| README.md | ||
| selene.toml | ||
| stylua.toml | ||
| vim.toml | ||
blink-cmp-ghostty
Ghostty configuration completion source for blink.cmp.
Features
- Completes Ghostty configuration keys with documentation
- Provides enum values for configuration options
- Documentation extracted from
ghostty +show-config --docs
Requirements
Installation
Install via luarocks:
luarocks install blink-cmp-ghostty
Or with lazy.nvim:
{
'saghen/blink.cmp',
dependencies = {
'barrettruth/blink-cmp-ghostty',
},
opts = {
sources = {
default = { 'ghostty' },
providers = {
ghostty = {
name = 'Ghostty',
module = 'blink-cmp-ghostty',
},
},
},
},
}