Turns out all the problems were because of the shallow clone that I got originally when first getting the repo months (or years) ago. This seems to prevent seeing all branches and whatnot.
I deleted everything , and found a solution at http://leoeditor.com/installing.html#installing-leo-from-sources-all-platforms with *git clone --single-branch -b devel --depth=200 https://github.com/leo-editor/leo-editor.git* This gave me a new repo that is on the 'devel' branch! (this inverted the problem : its the only branch it seems to be aware of when i do "git branch -r" ) I still dont know how to how to switch from/to remote branches from the Leo main repo but at least I've got a way to get either branch individually ! :) (This stackoverflow solution seemed to be a good way to get all branches: https://stackoverflow.com/questions/12762922/git-cannot-see-new-remote-branch but it started a MASSIVE download that I killed with ctrl+break and restarted all with the solution above in bold...) This adventure in trying to switch to the devel branch of leo really got me aware of how little i really know what I'm doing with git! -- Félix On Monday, June 15, 2020 at 5:39:29 PM UTC-4, Félix wrote: > > I feel a bit stupid for this but I cannot seem to be able to switch to the > 'devel' branch as much as I try... I only see master, head, and branches > with names for Leo's releases (6.1, 5.4, etc.. ) (I'm not an expert at all > with GIT) > > Here is my console with stuff I tried: > > If I use the UI for git related stuff in vscode I see this : > > > Or is it this one? > > > > Anyways thanks in advance for any pointers ... I thought it would be a 5 > second thing like "*git checkout devel*" but I've been checking for all > sorts of ways in google on how to 'switch to a remote branch from github" > online for a few hours now... lol So I going to stay on Leo's master > branch 6.2.x for now hehe.. > > Félix > > > > On Monday, June 15, 2020 at 8:09:32 AM UTC-4, Edward K. Ream wrote: >> >> On Sun, Jun 14, 2020 at 10:46 PM Félix <[email protected]> wrote: >> >> Getting the basic "general" Leo color syntaxing was not that hard once I >>> finally understood the 'textMate' standard for specifying tokenization >>> rules! >>> >> >> Excellent! >> >> live on branch #37 as of now, and soon to be on the dev and master branch >>> in a couple of hours. :) >>> >> >> Here are some links that I have bookmarked: >> >> - leointeg main github page <https://github.com/boltex/leointeg> >> - leointeg issues <https://github.com/boltex/leointeg/issues> >> - leointeg PR's <https://github.com/boltex/leointeg/pulls>, for example, >> #37 & #54. >> - leointeg theory post >> <https://groups.google.com/forum/#!msg/leo-editor/gZP1WdiY4b0/YXTv6ay_BgAJ> >> >> I am starting to understand how all the pieces fit together. I'll present >> my own summary in another post for your comments and corrections. >> >> 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/c8db3b11-fc94-4151-a821-4850262d56b7o%40googlegroups.com.
