lagergren

Language Support for XTC (Ecstasy)

Executive Summary

This document outlines a comprehensive plan to create IDE-independent language support for XTC (Ecstasy), leveraging modern protocols like LSP, DAP, and TextMate grammars to provide syntax highlighting, code intelligence, debugging, and more across multiple IDEs.

Table of Contents

1. Understanding XTC/Ecstasy
2. Current State of Tooling

lagergren

~/src/zombiesnack compose-cleanup *1 !4 ?1 ❯ time pyright                                                                                                                                                                                                                                               х INT Py thaum marcus@thaum 10:04:55
WARNING: there is a new pyright version available (v1.1.359 -> v1.1.361).
Please install the new version or set PYRIGHT_PYTHON_FORCE_VERSION to `latest`

/home/marcus/src/zombiesnack/src/camera/femtomega/camerasettings.py
  /home/marcus/src/zombiesnack/src/camera/femtomega/camerasettings.py:23:12 - error: Operator "/" not supported for types "MatLike" and "int"
    Operator "/" not supported for types "NumPyArrayGeneric" and "int" (reportOperatorIssue)
/home/marcus/src/zombiesnack/src/hyperformer/hyper_aloha/hyperspace_aloha.py
  /home/marcus/src/zombiesnack/src/hyperformer/hyper_aloha/hyperspace_aloha.py:322:20 - error: Operator "|" not supported for types "dict[str, Any]" and "Unk

lagergren

diff --git a/javatools_backend/build.gradle.kts b/javatools_backend/build.gradle.kts
new file mode 100644
index 000000000..63dea1e2f
--- /dev/null
+++ b/javatools_backend/build.gradle.kts
@@ -0,0 +1,33 @@
+/**
+ * Experimental Javatools backend.
+ */
+

lagergren

This is normally not the Docker approach. 
Volumes only exist during runtime, and any changing external source is usually retrieved on volume level and during startup
There may be use cases when you want to clone something from git during the Dockerfile during build, but they are not very common. 
To clone a particular repo as part of the container build do: 

ADD https://api.github.com/repos/org/reponame/git/refs/heads/$GITHUB_BRANCH version.json
RUN git clone --branch $GITHUB_BRANCH --depth=1 https://github.com/org/reponame repo

The verison.json will ADD will create a layer that is invalidated iff $GITHUB_BRANCH is updated, and then, rebuilding the container will
realize that this layer will be regenerated.