[FEATURE] Add syntax highlighting for 1C:Enterprise (BSL) language

Status Open
Maintainer reply None cached
Activity 3 comments · opened Dec 29, 2025

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

1C:Enterprise platform, which uses BSL language. Currently, the code appears as plain text.

Additional context

  • Language Name: 1C:Enterprise / BSL
  • Common Extensions: .bsl, .os (OneScript)

Proposed Solution

BSL is already supported by major syntax highlighting engines including PrismJS, Shiki, and Pygments, so integration should be straightforward.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] · 7 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

fserg · 7 months ago

Hi!
Just wanted to say that this issue is really important for us. We work with BSL / 1C code on a daily basis, and without syntax highlighting it’s quite hard to use Claude Code comfortably.

We’d really appreciate it if this could be considered. Thanks!

RooLee10 · 7 months ago

Hi team — this feature is important for many of us who work with 1C:Enterprise / BSL every day.

Without syntax highlighting, reading and reviewing BSL snippets in Claude Code is slow and error‑prone (it’s easy to miss keywords, strings, and comments), which directly reduces the tool’s usefulness for real projects. With highlighting, the same code becomes immediately scannable and safe to edit.

BSL already has existing highlighters (e.g., Prism/Shiki/Pygments implementations), so integrating support should be relatively straightforward compared to adding a brand‑new language. Please consider keeping this issue open and prioritizing it—this would make Claude Code significantly more usable for a large community of 1C developers.