Re: [QA]how to define Syntax coloring for GLOBAL var?

On Tuesday, December 5, 2017 at 12:09:15 PM UTC-6, Edward K. Ream wrote: The keys in the python_main_keywords_dict must be strings, not regular > expressions. However, it definitely would be possible to add entries to > the rules dict: > Several additional comments: 1. Everything should "just

Re: [QA]how to define Syntax coloring for GLOBAL var?

I am going to edit the original question for clarity. Everything in [square brackets] are my edits. Please correct me if I have misunderstood anything. This is a very interesting question. It raises possibilities that I never considered before. On Wednesday, November 29, 2017 at 7:21:17 AM U

Re: Leo's usage tips

On Tue, Dec 5, 2017 at 11:04 AM, Terry Brown wrote: > ​I agree. Closed == Harvested.​ > > I'd say Closed == complete / ready for use. Whenever the db shipped > with Leo is regenerated, it could harvest all closed issues tagged with > Tip. > ​Ok. This seems like a good work flow.​ > > More spe

FYI: The more issues the better

In Leo, we use leo-editor for many conversations, but the standard practice in many projects is to use the project's GitHub tracker for virtually *all *communications. This is reasonable, but I prefer to have issues be related to projects or sub-projects. In any case, I want to encourage peopl

Re: Leo's usage tips

On Tue, 5 Dec 2017 10:53:47 -0600 "Edward K. Ream" wrote: > > So while we could close tips > > ​ ​ > > to indicate they're complete, I think GitHub could be their > > canonical ​ ​ > > source. Makes it easy to edit and update them. > > ​I agree. Closed == Harvested.​ I'd say Closed == complete

Re: Leo's usage tips

On Tue, Dec 5, 2017 at 10:53 AM, Edward K. Ream wrote: > On Tue, Dec 5, 2017 at 10:45 AM, Terry Brown > wrote: > If we're going to manage tips on GitHub, the could be harvested from >> there automatically, using GitHub's API. > > > ​I didn't know that ;-) > ​Is this

Re: Leo's usage tips

On Tue, Dec 5, 2017 at 10:45 AM, Terry Brown wrote: Although I think Vitalije's spread sheet to collect tips was workable, > GitHub has the advantage of having markdown rendering. > ​There are many other advantages. ​ > If we're going to manage tips on GitHub, the could be harvested from > ther

Re: Leo's usage tips

Although I think Vitalije's spread sheet to collect tips was workable, GitHub has the advantage of having markdown rendering. If we're going to manage tips on GitHub, the could be harvested from there automatically, using GitHub's API. So while we could close tips to indicate they're complete, I

Re: Leo's usage tips

On Tuesday, November 28, 2017 at 8:39:28 AM UTC-6, vitalije wrote: I have just created a new issue > , and want to > discuss it here. > I have just created my top 5 tips. I encourage others to do the same. You can find all my tips using the

Re: Leo's usage tips

On Tue, Dec 5, 2017 at 10:08 AM, xgid wrote: > do you think that it may be useful to have also some kind of "difficulty > level" tag for each tip? > ​Sure. One of the tags I used was "Beginner". Edward -- You received this message because you are subscribed to the Google Groups "leo-editor

Re: Refresh of recommended plugins

On Tue, Dec 5, 2017 at 7:15 AM, lewis wrote: What exactly are Qt-related plugins? > ​ ​ > How are they different than the *Qt only plugins* listed at > http://leoeditor.com/plugins.html? > ​ ​ > leoSettings.leo file has a number of Qt plugins in the recommended plugins > list. > ​I was referring

Re: Refresh of recommended plugins

On Tuesday, December 5, 2017 at 10:15:41 PM UTC+11, Edward K. Ream wrote: > > > > ​The @enabled-plugins nodes in leoSettings.leo contains a list of > recommended plugins.​ > > There is no need to enable the importer, writer or Qt-related plugins. > The Qt-related plugins appear in leoPy.leo, not

Re: Leo's usage tips

On Tue, Dec 5, 2017 at 5:50 AM, Edward K. Ream wrote: > On Tue, Nov 28, 2017 at 8:39 AM, vitalije wrote: > > I have just created a new issue >> , and want to >> discuss it here. >> > > ​Excellent. I am editing this issue as I type this. > ​I

Re: Leo's usage tips

On Tue, Nov 28, 2017 at 8:39 AM, vitalije wrote: I have just created a new issue > , and want to > discuss it here. > ​Excellent. I am editing this issue as I type this. Imo, using Leo's existing issue tracker is a far better way to keep tra

Re: Refresh of recommended plugins

On Fri, Dec 1, 2017 at 11:21 AM, Matt Wilkie wrote: My myLeoSettings.leo file is now years old and there's a lot of stuff in > there that is no longer as relevant and sometimes at cross purposes to > today's best practices. Of particular interest to me today are plugins. > What are the current be