On Wed, Mar 29, 2017 at 6:47 AM, Edward K. Ream <[email protected]> wrote:
> On Wed, Mar 29, 2017 at 2:36 AM, vitalije <[email protected]> wrote: > > There was attached file >> <https://11707503125000652521.googlegroups.com/attach/63f325cf79f6b2e9/nosent-goto-line-bug.leo?part=0.1&vt=ANaJVrEFOqs7FjwohsShTGNcPvTY-neL0Bo1HM69Du4ut9S9FNhvRdiBCr5P9xR8iVVp53Mv15nj28FJb7AWRn6WCrWuTp12GR91I-HvbIlypzqXs6SVYh8>. >> I have just updated my Leo and tested this file and once again >> goto-global-line is not working correctly. >> > > Excellent. I'll create an issue for this. Thanks! > Done: #452: goto-global-line problems <https://github.com/leo-editor/leo-editor/issues/452>. There seems to be a problem only when no @language in effect, or, maybe, when there is a mismatch between the computed @language and the proper @language. I conjecture that this could happen when using a clone of a node. For sure, the @<file> node's file extension should determine comment delims in the absence of any @language directive in the root node. This probably *is* true when writing the file, but probably *isn't* true when executing Alt-G. In short, this is a subtle, probably rare, problem. 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. 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
