Re: I've declared war on fit and finish problems :-)

On Sat, Apr 1, 2017 at 2:48 PM, Xavier G. Domingo wrote: > OK, I've created all of them: > >- https://github.com/leo-editor/leo-editor/issues/453 >- https://github.com/leo-editor/leo-editor/issues/454 >- https://github.com/leo-editor/leo-editor/issues/455 >- https://github.com/leo

Re: I've declared war on fit and finish problems :-)

OK, I've created all of them: * https://github.com/leo-editor/leo-editor/issues/453 * https://github.com/leo-editor/leo-editor/issues/454 * https://github.com/leo-editor/leo-editor/issues/455 * https://github.com/leo-editor/leo-editor/issues/456 * https://github.com/leo-editor/leo-editor/iss

Re: I've declared war on fit and finish problems :-)

Since version PyQt5 5.8.1 Leo has continued to report the version as 5.8.0 in the log file. This is still the case with PyQt5 v5.8.2 I'm not sure if this is an issue with PyQt5 or Leo. I have confirmed my installed PyQt5 version as 5.8.2 with 'pip list'. *Leo Log WindowLeo 5.5, build 20170

Re: I've declared war on fit and finish problems :-)

On Wed, Mar 29, 2017 at 10:28 PM, Xavier G. Domingo wrote: > Another minor bug: > > I make a search of a text in the entire outline with the "wrap Around" > option activated. I start the search in the middle of the outline, find > some matches in several nodes and keep pressing F3 until I reach t

Re: I've declared war on fit and finish problems :-)

On Wed, Mar 29, 2017 at 10:58 AM, Xavier G. Domingo wrote: > Oh, another one: > > The size of the Chapters drop-down list is not resized when new "@chapter" > directives are added to headlines which are longer than the previously > existing ones, so the new chapter names cannot be read: > > > > T

Re: I've declared war on fit and finish problems :-)

On Wed, Mar 29, 2017 at 10:15 AM, Xavier G. Domingo wrote: > > I've recently found 3 minor issues that may or may not be included in this > category: > 1. Focus jumps to de body pane when expanding an abbreviation in a > headline (we had already commented this in another issue) > 2. Focus jumps t

Re: I've declared war on fit and finish problems :-)

Another minor bug: I make a search of a text in the entire outline with the "wrap Around" option activated. I start the search in the middle of the outline, find some matches in several nodes and keep pressing F3 until I reach the end of the outline. Then the search goes on and finds some othe

Re: I've declared war on fit and finish problems :-)

And just right now I've come across another issue, this time is a performance one: If I make a Search and Replace of a simple string (".html" to ".htm") and press the "Replace All" button with the option "Node only" in a node with about 370 lines of text (approx. 40,000 chars) in its body, the

Re: I've declared war on fit and finish problems :-)

Oh, another one: The size of the Chapters drop-down list is not resized when new "@chapter" directives are added to headlines which are longer than the previously existing ones, so the new chapter names cannot be read: This is only fixed by closing and opening again the .leo file. Or maybe

Re: I've declared war on fit and finish problems :-)

> This kind of fit and finish problem undermines people's confidence in Leo's overall quality. I consider all such problems to be extremely serious. That's a wise attitude. I've recently found 3 minor issues that may or may not be included in this category: 1. Focus jumps to de body pane when

Re: I've declared war on fit and finish problems :-)

On Wed, Mar 29, 2017 at 6:47 AM, Edward K. Ream wrote: > On Wed, Mar 29, 2017 at 2:36 AM, vitalije wrote: > > There was attached file >>

Re: I've declared war on fit and finish problems :-)

On Wed, Mar 29, 2017 at 2:36 AM, vitalije wrote: I remember posting an example leo file that demonstrates problems with > goto-global-line. Here is the original post https://groups.google.com/ > forum/#!searchin/ >

Re: I've declared war on fit and finish problems :-)

> For example, I recently ignored an apparent problem with Alt-G, > goto-global-line. It would have been best to *stop everything* and make > careful notes about how to recreate the problem, but I didn't do that. Now > I can't find anything wrong with Alt-G. Live and learn. I remember posti

Re: I've declared war on fit and finish problems :-)

On Tuesday, March 28, 2017 at 2:48:43 PM UTC-5, Edward K. Ream wrote: > I just created #451 for this. Fixed at 3c54f4c . Afaik, @auto-rst is working

Re: I've declared war on fit and finish problems :-)

On Tuesday, March 28, 2017 at 2:29:28 PM UTC-5, Edward K. Ream wrote: > > > > > My biggest peeve is refresh from disk selecting the top node in the >> outline after reload. Sometimes. Do others see that? >> > > ​I'll look into this as part of the work concerning @auto-rst and > refresh-from-di

Re: I've declared war on fit and finish problems :-)

On Tue, Mar 28, 2017 at 12:30 PM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: Should we have a fit_and_finish label on github? > ​I regard all such issues as real bugs. ​ > My biggest peeve is refresh from disk selecting the top node in the > outline after reload. Someti

Re: I've declared war on fit and finish problems :-)

On Tue, 28 Mar 2017 10:05:14 -0700 (PDT) "Edward K. Ream" wrote: > The new focus code is the opening shots in this war. I want Leo to be > work *perfectly*. > > The challenge is to have fit and finish problems rise to full > consciousness while I am working on other things. Been there. Should

I've declared war on fit and finish problems :-)

The new focus code is the opening shots in this war. I want Leo to be work *perfectly*. The challenge is to have fit and finish problems rise to full consciousness while I am working on other things. For example, I recently ignored an apparent problem with Alt-G, goto-global-line. It would ha