Editor support generalized: shared core, language server, Vim and VS Code (from dev eb5baf9cbe59)
doc/edit/ now holds a shared Python implementation of the language's structural layer (klammertext_edit.py) and a dependency-free language server (klammertext_ls.py), with integrations for Emacs, Sublime Text, Vim, and Visual Studio Code. The editor test suite in tst/ covers the core's API and CLI, the language server protocol, the VS Code extension, headless Vim, and Emacs byte-equality. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -48,11 +48,14 @@
|
||||
;; Known limitation: a raw @ inside a ^'...'^ literal region would confuse
|
||||
;; the depth scan (the same limitation as the font-lock scanner).
|
||||
;;
|
||||
;; SYNC: the Sublime Text port doc/sublime/Klammertext_indent.py duplicates
|
||||
;; this file's policy (a Sublime plugin cannot read these defcustoms). When
|
||||
;; you change `klammertext-indent-offset', `klammertext-transparent-klammers'
|
||||
;; or `klammertext-code-klammers', mirror the change in that file's
|
||||
;; INDENT_OFFSET / TRANSPARENT_KLAMMERS / CODE_KLAMMERS.
|
||||
;; SYNC: the shared Python core doc/edit/shared/klammertext_edit.py — the
|
||||
;; single implementation behind the Sublime, Vim, and VS Code integrations
|
||||
;; and the language server — carries this file's policy as INDENT_OFFSET /
|
||||
;; TRANSPARENT_KLAMMERS / CODE_KLAMMERS (an elisp defcustom cannot be read
|
||||
;; from Python, so this unit remains an independent implementation, held
|
||||
;; equal by tst/editor_test.sh's byte-equality checks). When you change
|
||||
;; `klammertext-indent-offset', `klammertext-transparent-klammers' or
|
||||
;; `klammertext-code-klammers', mirror the change there.
|
||||
|
||||
;;; Code:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user