Terry, that seems like a terrific idea. Can't think of why it wouldn't work.
Rob........... On Friday, January 29, 2016 at 3:10:19 PM UTC-5, Terry Brown wrote: > > Git *users* can create gists, like https://gist.github.com/tbnorth/6165576 > > But https://github.com/leo-editor is a GitHub organization, not user, so > it doesn't have gists, instead I made a separate repo. all members of > leo-editor can push to: https://github.com/leo-editor/snippets > I'd vote for that. There's more junk, um, I mean invaluable and > educational examples :-), laying around at the top level than there should > be, but as long it doesn't get worse and people (myself included) remember > to put things in subfolders going forward, I think it will be ok. > > Does that seem like a workable option to you? If it needed to look > prettier, we could use github pages to make an index or something. > > BTW, anyone know how to stop google-groups hiding my email address ( > terry_...@yahoo.com <javascript:>)? I can't find the setting. > > Cheers -Terry > > ------------------------------ > *From:* Largo84 <lar...@gmail.com <javascript:>> > *To:* leo-editor <leo-e...@googlegroups.com <javascript:>> > *Sent:* Friday, January 29, 2016 1:57 PM > *Subject:* Re: Code Academy: real Leo programmers use git > > This is all great stuff. Yes, been using Git for a while now to stay > current on the code base. I've often wondered if there's also an easier way > to share code snippets and scripts. There's Leo wiki > <http://leo.zwiki.org/LeoWiki> that would be ideal for that, but it > hasn't been edited in over 4 years. Is that something that can be revived? > > Rob........... > > On Friday, January 29, 2016 at 11:37:59 AM UTC-5, Edward K. Ream wrote: > > If you are going to do interesting work on Leo and its plugins, you should > be using Leo’s latest sources <https://github.com/leo-editor/leo-editor> > from GitHub <https://github.com/leo-editor> using git > <http://git-scm.com/>. Once git is installed, getting the latest version > of Leo is easy: > > git clone https://github.com/leo-editor/ leo-editor.git > <http://github.com/leo-editor/leo-editor.git> > > Once you have done that, you can get the latest sources with: > > git pull > > Git is great in tracking history and reverting unwanted changes. And it > has many other benefits. > > I've been wondering when to say this, but recent developments have forced > my hand. Today, as the result of our Code Academy discussion, I have added > the p.u property and a keyword arg to c.editCommands. deleteNodeIcons. If > you don't use git you will quickly get out of the loop. > > Although git is unique behind the scenes, using git is very similar to > using bzr or hg or any other SCCS. To change Leo, you add files, you > commit files, and you push files. That's about it. > > I'll be happy to answer any git-related questions here. Again, I > *strongly* encourage all would-be Leo programmers to use Leo's git repo. > > 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 leo-editor+...@googlegroups.com <javascript:>. > To post to this group, send email to leo-e...@googlegroups.com > <javascript:>. > Visit this group at https://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. > > > -- 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.
