That's great news to wake up to! about the p.p.s. of leo's settings:
Worth noting that leoInteg checks with Leo's real settings that you might have set in Leo, for defaults regarding derived files, for example, So someone might use Leo, change those, and confidently switch back to using Leo via leoInteg, and those settings would apply. It's somewhat important to specify the concept that leoInteg is not trying to hide or replace Leo by implementing it's functionality in js/ts... To the contrary: It's shamelessly openly exposed as a 'facade', and the real Leo is running behind. No wizard of 'Oz' here :) On Sunday, June 21, 2020 at 9:54:26 AM UTC-4, Edward K. Ream wrote: > > This 10-minute video <https://www.youtube.com/watch?v=u21W_tfPVrY&t=317s> > is an excellent way to come up to speed with vs-code. It clearly shows why > vs-code is so popular. > > I have spent over an hour carefully working my way through the video, > trying most of the examples and installing most of the plugins. Already I > feel comfortable with vs-code. > > Imo, it's impossible for Leo's devs to keep pace with vs-code. Supporting > leoInteg seems like the way to keep Leo healthy and relevant. > > Edward > > P.S. Would it be worthwhile to rewrite the essentials of Leo's core in > typescript? That way leoInteg would not need any client/server architecture. > > The answer is "heck no!" leoInteg already has access to Leo's bridge. > Rewriting the bridge in typescript would be a distraction, it would > introduce many subtle bugs, and would have no obvious value. > > P.P.S. Which Leo settings will remain important? > > vs-code already has a more flexible key-binding scheme than Leo's. You can > see this by looking at the "When" column in the "Keyboard Shortcuts" pane. > This column contains (I think) an arbitrary expression. The binding is > active only if that expression evaluates to true. > > Many Leo's settings relate to editing functions that (in the vs-code > world) are better handled using existing vs-code settings. Similarly, Leo > settings relating to themes and other visual matters are not needed when > using vs-code. > > Leo settings relating to Leo-specific commands should remain. That > includes Leo's abbreviations. That might be a big job, but I think it would > be worth doing. > > 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/2e40d56f-3820-4a40-b33d-d9efa55b5199o%40googlegroups.com.
