Re: Proposal: Use the GitHub issue tracker instead of this forum

Although I'd probably recommend Gmail on line in general for email management, I use Clawsmail, http://www.claws-mail.org/, which is fast and extensible. I added a button to let you write email in restructuredText, along with colored syntax highlighting via. Pygments.  A long time ago, I'd have

Re: Proposal: Use the GitHub issue tracker instead of this forum

On Sunday, November 6, 2016 at 8:01:53 AM UTC-6, Edward K. Ream wrote: > > Several high-profile projects now use GitHub their issue tracker for *all* > discussions. > > There are substantial benefits to doing so, as I have just discovered: > The advantages of composing in GitHub are *huge*. I'll

Re: A note on testing

On Tuesday, November 8, 2016 at 9:55:35 AM UTC-6, Edward K. Ream wrote: I just said this in a comment for #334 , but I want to make sure everyone sees it. It applies to almost all the work that I do. It's not easy to undo the unfortunate

A note on testing

I just said this in a comment for #334 , but I want to make sure everyone sees it. It applies to almost all the work that I do. The code base [for Leo's importers] will be under considerable flux, but all should be well as long as all

Re: Proposal: Use the GitHub issue tracker instead of this forum

Hi, I think this is a good and convenient approach. On the issue of GitLab, this is a commercial product, but you can have free repositories as in GitHub. Fossil has another workflow, more fluid and less intrusive, IMO. For me is pretty convenient, but most of the imagination/thinking on

Re: Proposal: Use the GitHub issue tracker instead of this forum

On Tue, Nov 8, 2016 at 9:24 AM, Chris George wrote: > gitlab offers more than github for free. For example: it allows private > repositories, no cost. > ​Thanks. I'll investigate further. EKR -- You received this message because you are subscribed to the Google Groups

Re: Proposal: Use the GitHub issue tracker instead of this forum

gitlab offers more than github for free. For example: it allows private repositories, no cost. Chris On Tue, Nov 8, 2016 at 7:08 AM, Edward K. Ream wrote: > > > On Sun, Nov 6, 2016 at 5:33 PM, Chris George wrote: > >> Re centralization: I have been

FYI: #334: Simplify Leo's importers as much as possible

Per our recent discussions, I have started issue #334 to track work on Leo's importers. I am cross-referencing it here to make sure everyone sees it. Simplifying importers is crucial so that future devs can add importers and fix existing

Re: Python Anywhere

On Sunday, November 6, 2016 at 10:17:52 PM UTC-6, Chris George wrote: 1. There are somewhere around a million lines of Python code in Leo's core > and plugins. Thus, a *solid* python in javascript system is required. This > isn't likely to happen. > ... > It looks like at least the first

Re: Proposal: Use the GitHub issue tracker instead of this forum

On Sun, Nov 6, 2016 at 5:33 PM, Chris George wrote: > Re centralization: I have been using gitlab for a while. It offers all and > more than github for free and even allows you to install the code to run on > your own server. > > gitlab.com > ​This looks like a commercial

Re: Proposal: Use the GitHub issue tracker instead of this forum

On Sun, Nov 6, 2016 at 9:24 AM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: > > Personally I'd be fine with that, but I think it will be hard to get > more than 50% adoption, so things will still be split. ​As always, thanks for your excellent comments. > So... it would

Re: Proposal: Use the GitHub issue tracker instead of this forum

On Sun, Nov 6, 2016 at 5:33 PM, Chris George wrote: > > Re centralization: I have been using gitlab for a while. It offers all and > more than github for free and even allows you to install the code to run on > your own server. > > gitlab.com > ​Thanks for this link!

Re: About viewrendered

On Sun, Nov 6, 2016 at 10:19 PM, Chris George wrote: > Just noticed this: I use python 3.5.2 constantly. I already knew that PyQt > 5.7 breaks viewrendered. Working on it a bit, so does PyQt 5.5.1. > > But 5.6 works just fine. > ​Thanks, Terry and Chris, for your

Re: About viewrendered

On Mon, Nov 7, 2016 at 7:48 AM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: > On Sun, 6 Nov 2016 20:19:54 -0800 (PST) > Chris George wrote: > > > Just noticed this: I use python 3.5.2 constantly. I already knew that > > PyQt 5.7 breaks viewrendered.