Re: @nosent goto line bug

2015-02-26 Thread Edward K. Ream
On Thu, Feb 26, 2015 at 3:28 AM, vitalije vitali...@gmail.com wrote: Again, I have read in another thread: Leo 5.1 will be soon released. Just to bring Edward's attention to this thread and the fact that this bug has not been fully fixed yet. ​Don't panic :-) b1 won't go out the door until

Re: @nosent goto line bug

2015-02-26 Thread vitalije
Again, I have read in another thread: Leo 5.1 will be soon released. Just to bring Edward's attention to this thread and the fact that this bug has not been fully fixed yet. Vitalije. -- You received this message because you are subscribed to the Google Groups leo-editor group. To unsubscribe

Re: @nosent goto line bug

2015-02-24 Thread vitalije
Fixed at rev 3ee6afd. Let me know if you find any further problems. I must admit it seemed to me that this bug was fixed, but here is another example that demonstrate error in goto-global-line. In attached Leo file I just put one organizer node and goto-global-line can not find any

Re: @nosent goto line bug

2015-02-23 Thread Edward K. Ream
On Monday, February 16, 2015 at 1:08:45 PM UTC-6, vitalije wrote: I have just filled a bug report https://github.com/leo-editor/leo-editor/issues/138 Fixed at rev 3ee6afd. Let me know if you find any further problems. EKR -- You received this message because you are subscribed to the

Re: @nosent goto line bug

2015-02-15 Thread Edward K. Ream
On Sunday, February 15, 2015 at 12:41:44 PM UTC-6, vitalije wrote: For quite a long time I have noticed that command goto global line (Alt+G) doesn't work properly on @nosent files. It seems that it counts non-existing sentinel lines so it positions cursor few lines before the requested.