Skip to content

Known limits

  • macOS on Apple Silicon only, macOS 14 or later. There is no Intel build in the alpha.
  • No Linux or Windows, deliberately. crc talks to Metal and CoreText directly; a port would mean writing a second backend from scratch. See Architecture.
  • Highlighting covers the listed languages. Each grammar is vendored generated C pinned in third_party/CHECKSUMS. SQL is not in the alpha.
  • Five language servers, and no code actions from them.
  • No minimap.
  • Panes are a way of looking. A file is open in one pane at a time, and a restored session puts every pane’s files into one pane.
  • Bounded by design. Project search skips files over 2 MiB and shows the first 500 matches. The bracket matcher counts its own pair only and does not skip strings or comments.
  • Text input is new. Dead keys and IME go through macOS text input and need wider testing across layouts.
  • Gutter marks compare with HEAD, not the index, and stop at 2 MiB.
  • Hunk staging covers tracked text changes; other change types use whole-file actions.
  • Pull is fast-forward only, and crc has no merge or rebase command of its own. Conflicts from one you ran are resolved in crc; finishing, continuing or aborting it is Git’s.
  • Conflict markers are Git’s default seven characters. A custom conflict-marker-size is not recognised, and files over 16 MiB are not scanned for conflicts.
  • Files over 512 MB open read-only; files over 2 GB are refused. Both say why.
  • Crash recovery covers crashes in crc’s own code, not a power cut.
  • Updates are announced, not installed. Once a day crc asks GitHub whether a newer release exists and says so in the status line. Nothing is downloaded. update_check = false turns the check off.
  • Extensions are new and narrow. They can read and replace the selection or the document and add commands; nothing else yet. The signed registry is not live until its first release, so for now they install from a folder. See Extensions.