已归档:应用与游戏已迁入 emacs-taf 单一工作区(同级检出)
One workspace now owns every checkout. The application sources moved beside the framework packages in emacs-taf, and the shared checks, the application contract and the integration checkpoint live there. Keeping a second workspace meant a parallel registry plus a second copy of the tooling, which had already drifted from the root's (three different versions of check-api.py and run-acceptance.py, and two of check-repository.py). It also let one repository exist as two checkouts that diverged silently: the running Emacs loaded one while a later fix landed in the other. History stays readable; the repository is archived read-only and the README points at the workspace root. Validation: documentation-only dissolution, no checks run here; the relocated applications are covered by the workspace root `make check`. |
||
|---|---|---|
| LICENSE | ||
| README.md | ||
ETAF applications (archived)
This repository is archived. The application workspace it hosted was merged into
the single emacs-taf workspace, where
every repository — framework packages, applications and games — is one sibling
checkout registered in workspace.json.
- Sources: each application is its own repository under the
emacs-taforganisation (etaf-ncm,etaf-weread,etaf-md-preview, …). - Development: clone the workspace root and follow its README. There is one checkout per repository, so no second workspace has to be kept in sync.
- Installation:
M-x etaf-installfrom the package archive at https://etaf.top/packages/, or install a single package from MELPA-style archive metadata. - The application table, the application and integration contract, the shared
checks and the integration checkpoint moved to the workspace root repository
(
README.md,docs/architecture.zh-CN.md,workspace.json).
Git history here remains readable; nothing in it was rewritten.