On Wed, Jun 17, 2020 at 3:07 PM Félix <[email protected]> wrote:
Just a thought I often had: vscode is now, and going to be for many years, > the top editor used by the most people on the planet. It has dethroned > sublime-text, which had the crown for many years. (or belt, if you're a > wrestling fan) > I knew vscode was popular, but I didn't know it was that popular. See this survey <https://insights.stackoverflow.com/survey/2019#technology-_-most-popular-development-environments>. I'm shocked that so few devs use emacs. And it so happens that sublime is scriptable in python... And so I often > raged at myself for not doing a Leo integration when the target IDE would > have been python! There would have been no complicated websocket bridging > and all that ! just simple 'import leo.core.leoBridge as leoBridge' or > whatever, and directly call stuff in leoBridge.py... haha! (but i'm > oversimplifying obviously!) > Oh! I didn't get what you just said until the second time of reading! For pyzo, there is no need to transliterate your bridging code into python. Just use leo.core.leoBridge from pyzo! I'm stunned that I didn't think of this before! Or maybe I did think of it before, in a slightly different guise. Anyway, your work shows the scale of the effort required. There are two possibilities: 1. Add a "Leo plugin" to pyzo (ignoring the fact that pyzo doesn't support plugins). 2. Add a "pyzo plugin" to Leo. A feeble plugin, pyzo_in_leo.py, already exists. Either way, the amount of work to fully integrate Leo and pyzo would be comparable to your work with leoInteg. It hardly seems worth doing. I can't really comment on stuff relating to Vim and Emacs because I know > next to nothing about those except that they're popular editors with their > own 'system' of editing text. > > sorry for this rambling I'm going back to work on leoInteg now ! > This post has been earth shaking for me: I've spent the last several days delving into the innards of leobridgeserver.py and all the code on the JS side. The idea was to transliterate your typescript code into python. But there is no need to do this! There is no ts/python divide when supporting Leo inside pyzo. Just call the leoBridge! Furthermore, your work shows the scale of the effort required to do the pyzo_in_leo.py plugin properly. I doubt that this level of effort would ever be worthwhile. I'm dithering about leoEmacsInteg. True, few devs now use emacs. Otoh, I suspect millions of non-devs use org mode... btw last night I made ctrl+b on selected text a reality, - did'nt know this > handled @others and the like- and also fixed headline editing with double > quotes and special characters. So this makes it so that it is now possible > to re-do this video in its entirety. > https://www.youtube.com/watch?v=tuM8MvI9g6k Which I will do. : ) > Many thanks for your continued dedication to the leoInteg project. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS2%2B34iPwTD1VjQoGuh3_Vb8P6vHbLdS%3DP28tVH%3Dc4eGaQ%40mail.gmail.com.
