2 ms·
> "The org-mode reference is "rhetoric". That's the Latin for "#thatsthejoke" :)" I got what you were doing with it (suggesting it in a jokey way as if it woul
by ZenoArrow 9y ago
> "The org-mode reference is "rhetoric". That's the Latin for "#thatsthejoke" :)"
I got what you were doing with it (suggesting it in a jokey way as if it wouldn't be fair to even bring it up), I was just using it as an opening to discuss alternative org-mode implementations. Emacs may have the canonical one, but it's not like it's impossible to implement elsewhere.
> "Regarding the REPL - what I mean is, run a snippet that executes in the context of the editor"
Is that not covered by the Code Runner extension I suggested earlier?
> "And as for Git, I don't really understand the suggestion."
Multiple Git repos, each one covering different system settings. In other words, if you work across two PCs, one Git repo for PC 1, another Git repo for PC 2. Alternatively, you could organise it in the same repo under different branches. If you know Git you'll know what I'm suggesting is trivially easy.
- to3m 9y agoThe Code Runner looks like it just runs a script and puts the output in a VSCode panel, which is not the same thing. VSCode is written in something that compiles to Javascript, right? So, while you're running VSCode, there's a JS VM that's running the VSCode code. So what I'm missing is a way to be able to run your own code inside the same VM that the editor's code is running in, giving it full access to all the objects and state that the editor's code is in. You can use this to write ad-hoc extensions that disappear when you quit, or just experiment with the extension functionality. This is typically how you start and then iterate on extensions in Emacs.