3 ms·
> I want the editor to look at temporary buffers served up from the language server and have the code be “written” by sending the temporary buffer back to the l
by zarzavat 3y ago
> I want the editor to look at temporary buffers served up from the language server and have the code be “written” by sending the temporary buffer back to the language server which handles writing it out to files itself.
I don’t think any editor would want to accept this workflow. The biggest issue is that writing is reputation-critical, if the editor writes to the wrong place, or it fails to write when it should have written, then users lose their work which makes them very unhappy. So the editor has to take responsibility for doing the writing, and that is the user’s mental model when they save their work.
- fiddlerwoaroof 3y agoI want a system more like Bank Python[1] or Unison[2] or Pharo Smalltalk[3] that gets us beyond the idea of "code in files". And I have plans to build this on top of Common Lisp + SLIME [1]: https://calpaterson.com/bank-python.html https://calpaterson.com/bank-python.html [2]: https://www.unison-lang.org https://www.unison-lang.org [3]: https://pharo.org https://pharo.org
- pawelmurias 3y agoLoads of people absolutely hate having to use a weird custom IDE just to try a language. That's why all the smalltalk like things are doomed for failure unless they are enforced by a platform.
- fiddlerwoaroof 3y agoYeah, this is the problem my proposal solves.