Re: vs code plugin: git graph

2020-07-29 Thread Félix
Oh I get it, yes, They could have, yes, but the activity bar is in fact suggested as 'last resort' place to add buttons / ui elements, as it uses more space overall and requires exploration. It's suggested to (and easy once you're familiar with the api,) add buttons into other extension's

Re: vs code plugin: git graph

2020-07-29 Thread Edward K. Ream
On Wed, Jul 29, 2020 at 12:44 PM Félix wrote: > I was expecting to see something in the left had list of extensions. > > > What do you mean by this? > I should have used the term "activity bar". It contains icons for extensions. Right-clicking the bar allows us to show/hide icons for the

Re: vs code plugin: git graph

2020-07-29 Thread Félix
> > I was expecting to see something in the left had list of extensions. What do you mean by this? -- Félix On Wednesday, July 29, 2020 at 12:59:33 PM UTC-4, Edward K. Ream wrote: > > At last, an easy way to visualize git branch structure: vs code's git > graph >

vs code plugin: git graph

2020-07-29 Thread Edward K. Ream
At last, an easy way to visualize git branch structure: the git graph plugin. It's *much* better than gitk or anything else I have seen. Mission accomplished! The only glitch: By default it looks like you have to execute

Re: leo stops working

2020-07-29 Thread Thomas Passin
I have no experience with anaconda. It's conceivable (by which I suppose I mean "let's hope") that your problem is related to one I had a few days ago - see https://groups.google.com/forum/#!topic/leo-editor/5hcKMQ8ORxU On Wednesday, July 29, 2020 at 9:49:59 AM UTC-4, Geoff Evans wrote: > >

Re: leo stops working

2020-07-29 Thread GEOFFREY EVANS
Is there a version of Qt5/PyQt5 other than (better suited than) the one anaconda provides? On Wednesday, July 29, 2020, 10:01:20 a.m. NDT, Thomas Passin wrote: That's something nifty I didn't know. Otherwise, a segfault makes me think of something wrong (or missing) from Qt5/PyQt5.

Re: leo stops working

2020-07-29 Thread Thomas Passin
That's something nifty I didn't know. Otherwise, a segfault makes me think of something wrong (or missing) from Qt5/PyQt5. On Tuesday, July 28, 2020 at 6:47:22 PM UTC-4, Geoff Evans wrote: > > ... and when I start a python or ipython session (not specifying python3) > the @ operator for matrix