Re: Interesting article about WebAssembly

On Wed, Feb 27, 2019 at 8:16 AM Matt Wilkie wrote: > John posted this article in a Pharo thread, but I'm moving response here > because of the topic: > https://almarklein.org/python_and_webassembly.html > Great link. Thanks for sharing it. Edward -- You received this message because you are

Re: Windows: register .leo files with OS

On Thu, Feb 28, 2019 at 2:06 AM Matt Wilkie wrote: > Good news! The Register and Unregister scripts to enable/disable Windows > to start Leo from double-clicking on a .leo file now work. --- For me. > testing appreciated. > Many thanks for this work. Edward -- You received this message

Re: latex syntax coloring

On Wed, Feb 27, 2019 at 8:12 AM Rob wrote: > Duh! Just figured it out. `@language latex` and `@language tex` give > different results. > I have just created #1088 for this. Edward -- You received this message because you are subscribed

Re: Snippet for finding Leo's library

On Thu, Feb 28, 2019 at 12:41 AM Matt Wilkie wrote: > Nope, see https://gist.github.com/maphew/c4670b3cb6e045e7583769de6a185ee6. > > > I'm happy to create an issue if this is supposed to work. > It's only guaranteed to work in its specific context. Feel free to create an issue, so it will

Re: latex syntax coloring

> >- However, words after the closing `\` are improperly colorized. > > This needs fixing, because the "closing" "\ " designates really macro, which ends with the blank (and expands to a blank), since latex macros gobble up any trailing blank. I have such "\ " (backslash followed by a

Re: latex syntax coloring

Hi Rob, Thanks for figuring this out. I have always @language latex in my files, because that is what gets automatically added by Leo when opening a file with a .tex filename extension. Since latex and tex have the same syntax, I don't see why there should be two different syntax coloring

Windows: register .leo files with OS

Good news! The Register and Unregister scripts to enable/disable Windows to start Leo from double-clicking on a .leo file now work. --- For me. testing appreciated. The enhancement issue is https://github.com/leo-editor/leo-editor/issues/1012, but it's probably a good idea to open new issues