FLE LSP 📡

February 10, 2026 · View on GitHub

Go Report Card CI codecov

A high-performance Language Server Protocol implementation for Fast Log Entry (FLE) ham radio logbooks.

⚡ TL;DR: Quick Start

What is it? A tool that adds IDE-like features (errors, completions, formatting) to your FLE logging workflow.
Why use it? Catch logging errors instantly, automate formatting, and navigate thousands of QSOs with ease.
How to start?

  1. Build: go build -o fle-lsp ./cmd/main.go
  2. Configure: Add the binary to your PATH and point your favorite LSP client (VS Code, Neovim, etc.) to it.

✨ Features

FLE LSP transforms your text editor into a powerful radio logging workstation:

🔍 Real-time Intelligence

  • Instant Diagnostics: Catches syntax errors, invalid dates, and out-of-order timestamps as you type.
  • Smart Autocomplete:
    • Bands (160m - 70cm) and Modes (CW, SSB, FT8, etc.).
    • Dynamic current UTC time and date suggestions.
    • Header keywords (mycall, mygrid, operator, etc.).
    • MyGrid: Type mygrid to auto-suggest your current Maidenhead locator from:
      • GPS: Direct TCP link to local gpsd (supports cgps/gpsmon).
      • GPredict: Configured ground stations in ~/.config/Gpredict/.
      • Xastir: Station location from ~/.xastir/config/xastir.cnf.
  • Contextual Hover: Hover over any QSO to reveal:
    • Persistent state (Date, Band, Mode).
    • Contact Statistics: Number of times you've worked this callsign.
    • DXCC Info: Country and entity details (supports all countries + European microstates & French territories).
  • Quick Fixes: Automatically correct date formats (e.g., DD/MM/YYYY → YYYY-MM-DD).
  • GeoJSON Export: Instant export of your logs to a .geojson file for visualization in tools like geojson.io or QGIS. Uses standard window/showDocument to auto-open the result.

🛠️ Professional Layout & Formatting

  • Auto-Formatting: Automatically normalizes Maidenhead grids (e.g., jn38qr → JN38qr), callsigns, and modes.
  • Document Hierarchy: Navigate complex logs via a structured outline (Year > Month > Day > QSO).
  • Smart Folding: Collapse entire years or months to focus on your current session.
  • Inlay Hints:
    • Distance/Bearing: Instant calculations from your mygrid to the worked callsign.
    • Daily Statistics: Real-time QSO counts per session directly in the editor.
  • Semantic Highlighting: Rich, context-aware coloring for all FLE elements.

Tip

Use the included FLE Original theme in VS Code for the best semantic highlighting experience.

🚀 Editor Setup Guides

The Zed extension supports both LSP features and Tree-sitter highlighting.

  1. Download the zed-support folder.
  2. Open Zed and drag-and-drop the zed-support folder into the editor to install it as a Dev Extension.
  3. In your settings.json, configure the LSP path:
{
  "lsp": {
    "fle": {
      "binary": { "path": "/path/to/fle-lsp" }
    }
  },
  "languages": {
    "fle": {
      "semantic_tokens": "combined",
      "inlay_hints": { "show_background": true, "enabled": true }
    }
  }
}

Helix (hx)

  1. Add to your ~/.config/helix/languages.toml:
[[language]]
name = "fle"
scope = "source.fle"
injection-regex = "fle"
file-types = ["fle"]
comment-token = "#"
language-servers = [ "fle-lsp" ]

[language-server.fle-lsp]
command = "fle-lsp"
  1. Copy zed-support/languages/fle/highlights.scm to ~/.config/helix/runtime/queries/fle/highlights.scm for Tree-sitter support.

Neovim (Built-in LSP)

Add this to your init.lua:

-- Register .fle filetype
vim.filetype.add({ extension = { fle = "fle" } })

-- Attach LSP
vim.api.nvim_create_autocmd("FileType", {
  pattern = "fle",
  callback = function()
    vim.lsp.start({
      name = "fle-lsp",
      cmd = { "fle-lsp" },
      root_dir = vim.fn.getcwd(),
    })
  end,
})

VS Code

  1. Navigate to vs-code-support/ and run npm install.
  2. Open the folder in VS Code and press F5 to launch.

🛠️ Development

Local Build

go build -o fle-lsp ./cmd/main.go

Quality Control

make lint    # Run golangci-lint
go test ./... # Run full test suite

📚 Resources

Maintained by F4JXQ