Re: Any reason to keep @auto or @shadow?

On Fri, Feb 20, 2015 at 12:25 PM, vitalije wrote: > > Please take a look into global-goto-line bug > before releasing > 5.1, especially because it relates to @clean files, and I guess it wont be > too hard to deal with. > ​It will be fixed f

Re: Any reason to keep @auto or @shadow?

No, it can't be "frustrated", but it can be frustrating new users. Sorry, English is not my first language. > > Vitalije. > -- 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

Re: Any reason to keep @auto or @shadow?

> > I'll add support for @clean today. Leo 5.1 will come out in a few days. > > Edward​ > Please take a look into global-goto-line bug before releasing 5.1, especially because it relates to @clean files, and I guess it wont be too hard to

Re: uA's practical usage questions

That's great, just loaded the plugins and experiment. Thanks! Rob... On Friday, February 20, 2015 at 11:31:38 AM UTC-5, Jacob Peck wrote: > > uA's are really only useful with scripts and plugins -- but several > plugins use them to store data. For example, the nodetags.py plugin uses > the

Re: uA's practical usage questions

uA's are really only useful with scripts and plugins -- but several plugins use them to store data. For example, the nodetags.py plugin uses them to store tags. It has a UI that lets you deal with this rather than writing scripts :) There's also the attrib_edit.py plugin (I think?) which pro

uA's practical usage questions

After searching through LeoDoc.leo for help on uA's, I was able to determine only that it's an acronym for unknownAttibute and some technical programming notes that doesn't make much sense to me. It seems like a potentially useful tool, but I can't find anything on how to actually create (write

Re: @clean is now the preferred spelling of @nosent

After years of using (and benefitting from) Leo, I'm glad I could finally give something back:-) Rob... On Friday, February 20, 2015 at 10:30:24 AM UTC-5, Edward K. Ream wrote: > > I'll be updating the docs soon. > > If you decide to change lots of @nosent nodes to @clean nodes, be aware > t

@clean is now the preferred spelling of @nosent

I'll be updating the docs soon. If you decide to change lots of @nosent nodes to @clean nodes, be aware that you do can choose "cancel" when prompts warn that the @clean files have been changed outside of Leo. This will save the .leo file without you having to respond to a warning for each cha

Re: Any reason to keep @auto or @shadow?

On Fri, Feb 20, 2015 at 5:20 AM, Edward K. Ream wrote: > >> I'll add support for @clean today. > ​Done at rev 497a96c. All tests pass. Please report any problems immediately. If you decide to change lots of @nosent files to @clean files, be aware that you do can choose "cancel" when warning pr

Re: Any reason to keep @auto or @shadow?

On Fri, Feb 20, 2015 at 2:32 AM, jkn wrote: > > @nosent is not a good name; > ​...it took me a while to realize that it referred to (no) sentinels, > rather than something not being sent! > > There is a degree of cognitive dissonance to the '@no... ' form > ​...​ > > > @clean sounds like a good c

Re: Any reason to keep @auto or @shadow?

On Wednesday, 18 February 2015 07:07:10 UTC, Matt Wilkie wrote: > > > The only reason I can think of to prefer @auto is >> > > ...it's a better name. :) > > If @nosent is a synonym for @auto, then the code-that-used-to-be-called > @auto can be relegated to history and the code-that-is-now @nose