On Thu, 14 Apr 2016 14:44:47 -0500 "Edward K. Ream" <edream...@gmail.com> wrote:
> On Thu, Apr 14, 2016 at 2:41 PM, john lunzer <lun...@gmail.com> wrote: > > > Either way, I would guess it is not the desire nor the intention > > for Leo to lock up in this case. > > ​True, but it's *your* use case and your call. It's unreasonable to > expect Leo to guess what you want, or what the performance > implications are. In practice, you might want to split some of your > huge .leo files, or just do without the background checks. > > EKR I'm not sure that the current implementation is a great choice for on by default. John knows what's causing his problem, because it started when he flipped the setting. If it was on be default, working out why Leo's laggy would be hard, maybe you'd notice it was related to file access over a network, maybe not. Also, I find the immediate notification of change a bit intrusive, vs. only notifying when Leo regains focus, like Notepad++. Not sure if that would also help with John's problem. I hate to bring up the t word, but it might be possible to use a thread to cycle through checking files... maybe try the check on regaining focus only thing first though. Cheers -Terry -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
