Lukas Pistrol

My take on this is that we should enable it in our plugin API so plugin developers can choose what action they want to perform on "play". Similar to how...

I'll do that in the next few days!

@austincondiff nope not yet. Just everything that was implemented prior. Just moved from the `.json` file to `UserDefaults`

I'll dump some resources to consider here: * https://github.com/mchakravarty/CodeEditorView * https://github.com/dwarvesf/CodeViewer * https://github.com/ZeeZide/CodeEditor * https://github.com/twostraws/Sourceful * https://github.com/louisdh/savannakit

# Current State of the Editor I just want to publicly share what the current state of development of our core feature - the editor - is. ## Current Implementation...

Basic implementation of `tree-sitter` using [`SwiftTreeSitter`](https://github.com/ChimeHQ/SwiftTreeSitter/) and [`STTextView`](https://github.com/krzyzanowskim/STTextView) is now available on [`feature/new-editor`](https://github.com/CodeEditApp/CodeEdit/tree/feature/new-editor) branch. Contributions are welcome on the editor package [`CodeEditTextView`](https://github.com/CodeEditApp/CodeEditTextView)! Documentation is available [here](https://codeeditapp.github.io/CodeEditTextView/documentation/codeedittextview/). Thanks to @mattmassicotte for...

Yeah for now put it in `~/.codeedit/`. Once we decided where we want to put it for release we can move all files at once to minimize confusion among other...

Good idea but probably way out of scope for the initial `1.0` release

@SwiftUILabs The issue lies somewhere within [SwiftTerm](https://github.com/migueldeicaza/SwiftTerm) - the library `TerminalEmulator` relies on. Feel free to open an issue on their repo.

@SwiftUILabs: Unfortunately tree-sitter is a very complex topic and implementing it requires a lot of things to be figured out beforehand. So this will take some time.