Re: Proposed change to setup.py

[Matt Wilkie]

>
> With the confusions I've had using github forks, I think I'd like to work 
> in my own Mercurial repo, where I would only need my own code and not the 
> entire Leo distro, and copy the results to my Github fork of Leo.  For that 
> to work, the most convenient way would be for Leo to load plugins from the 
> PYTHONPATH instead of its own location.
>
> One of the github things that I haven't mastered is when I start a branch 
> for a project - say based off devel - and then that upstream branch changes 
> before I'm ready to merge or do a pull request.  Of course, this happens 
> all the time.  If I don't update my fork to upstream, then the merge or 
> pull request could involve all those other changed files that I wasn't 
> working on.  If I do update to upstream, then the update would step all 
> over my work, and I would have to copy my work back into the fork.
>
> Do you know how to make this all work?
>

One option is to enable the hg-git plugin, so you can continue to use 
Mercurial and push/pull from a git repo. I used this happily for a couple 
of years until a change in network policy at work blocked me from being to 
push outside the network.

As for not being clobbered by upstream changes or getting too far behind, I 
use 2 main strategies: 

a) keep your work in it's own folder within the repo, a place no one else 
is likely to touch. This is not possible if you need to touch core though. 
However this problem isn't solved by the off-campus route you're using now 
either.

b) merge early, merge often: as in daily. This way any given upstream 
change can (usually) be inspected and accepted/changed in small easy to 
understand pieces. Use an interactice tool like WinMerge or Kmeld to do the 
merging. (WinMerge has been easiest for me to understand, the keyboard 
shortcuts make sense to me.)

Really though if what you're doing now is successful keep doing it! VR3 is 
awesome. Better you spend your precious attention on building cool things 
like that than figuring out git arcana. ;-)

-matt

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/c4b7be62-c11e-452e-994f-1d1fdb2b0f90%40googlegroups.com.

Re: New installation log

[Matt Wilkie]

> OTOH, I have installed as a user on Linux distros many times using pip 
> install, and never had a problem. Never needed to consider using sudo.
>

Did/do you need to pass `--user` flag? 

pip install --user foobaz

I got into the sudo mess because I didn't know about the user flag, tried 
to just `pip install foo`, got a permission denied error, so reached for 
sudo out of habit, because that's what you need for apt installs. That's 
when I discovered conda and have stayed there since. It would be be good 
news if they've since made user installs the default. (I was on Mint 17 or 
18 if memory serves).

-matt

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/1881553d-55c4-43d5-9d8f-76b35f412ea2%40googlegroups.com.

Re: Release v6.2.1

[Matt Wilkie]

> Looks good to me. I'll release 6.2.1 tomorrow at the earliest.
>>
>  
> Hold please. TravisCI is failing on my latest checkin. 
> https://travis-ci.org/github/leo-editor/leo-editor/builds/668543463#L276
>

All good now. The fix was upgrading pip in the CI.

-matt

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/9c65792f-532c-4b33-83b9-9456376d0ec9%40googlegroups.com.

Re: Release v6.2.1

[Matt Wilkie]

>
> Looks good to me. I'll release 6.2.1 tomorrow at the earliest.
>
 
Hold please. TravisCI is failing on my latest checkin. 
https://travis-ci.org/github/leo-editor/leo-editor/builds/668543463#L276

-matt

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/dd9fa5eb-3b07-4932-959b-e09ffdb9eb85%40googlegroups.com.

Re: Leo's legacy layout is now the default in version 6.2

[Viktor Ransmayr]

Hello Thomas,

On Sun, Mar 29, 2020, 21:45 Thomas Passin  wrote:

> On Sunday, March 29, 2020 at 10:42:33 AM UTC-4, Viktor Ransmayr wrote:
>>
>> Hello Thomas,
>>
>> Am So., 29. März 2020 um 15:09 Uhr schrieb Thomas Passin <
>> tbp1...@gmail.com>:
>>
>>> I kind of get you there adding a setting
>>>
>>> @string central-dock-widget = outline
>>>
>>> I have attached a screen shot.
>>>
>>
>>
>> However, as you can see from the two screenshots attached Leo 6.1/
>> screenshot C - and - Leo 6.2/ screenshot D behave differently.
>>
>> What I would like to achieve is to get the default pane setup from 6.1
>> applied to 6.2!
>>
>> So far none of the suggestions work :-(
>>
>
> I have good news and bad news.  First, the good news  With the same
> @string as above,  I was able to drag the body and tabs panes to the new
> positions that you want.The attached image Leo version is with 6.3-devel,
> but I got the same results with 6.2-final.  This is on Windows, BTW.
>

Thanks for this update. - Lately I'm doing most of my work using Fedora 30.

I'll reserve some time to experiment further tomorrow night & will report
back ...

With kind regards,

Viktor

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAAeSrG%2BL2BMTpreyt0nXEi5y7iJYtAWKV5Q9Q2ZCj5KJH4ErkQ%40mail.gmail.com.

Re: Proposed change to setup.py

[Thomas Passin]

On Sunday, March 29, 2020 at 2:01:53 PM UTC-4, Matt Wilkie wrote:
>
>  
>
>> Then you could keep your development code entirely out of the repo until 
>> you got it to the point it was worth adding it in.  I'd like that.
>>
>
> A fork would accomplish this and then be easier to add to the main repo 
> later. I think so anyway, but there  might be things I'm not considering 
> that could make it more work than is desireable.
>

With the confusions I've had using github forks, I think I'd like to work 
in my own Mercurial repo, where I would only need my own code and not the 
entire Leo distro, and copy the results to my Github fork of Leo.  For that 
to work, the most convenient way would be for Leo to load plugins from the 
PYTHONPATH instead of its own location.

One of the github things that I haven't mastered is when I start a branch 
for a project - say based off devel - and then that upstream branch changes 
before I'm ready to merge or do a pull request.  Of course, this happens 
all the time.  If I don't update my fork to upstream, then the merge or 
pull request could involve all those other changed files that I wasn't 
working on.  If I do update to upstream, then the update would step all 
over my work, and I would have to copy my work back into the fork.

Do you know how to make this all work?

So until I learn how to avoid this problem, I need a place to develop my 
stuff that's outside of the fork.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/37f95744-6f13-4882-9da0-3fc459b567eb%40googlegroups.com.

Re: New installation log

[Thomas Passin]

On Sunday, March 29, 2020 at 2:49:30 PM UTC-4, vitalije wrote:

> On Sunday, March 29, 2020 at 8:21:05 PM UTC+2, Matt Wilkie wrote:
>
>
>> Linux can add a wrinkle with system vs user installs. User is safer in my 
>> experience. Morale of a painful story I havn't shared: *never use `sudo 
>> pip install`*. It can take a looong time to extricate from mixed up  
>> package manager installs and pip installs in system.
>>
>> -matt
>>
>>
> That's exactly why I prefer anaconda. It never  requires root privileges, 
> so there is no need for doing `sudo pip install`.
>

OTOH, I have installed as a user on Linux distros many times using pip 
install, and never had a problem. Never needed to consider using sudo.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/e8d6cd90-dcd5-4a95-8990-abfa736acbe2%40googlegroups.com.

Re: Leo's legacy layout is now the default in version 6.2

[Thomas Passin]

On Sunday, March 29, 2020 at 10:42:33 AM UTC-4, Viktor Ransmayr wrote:
>
> Hello Thomas,
>
> Am So., 29. März 2020 um 15:09 Uhr schrieb Thomas Passin <
> tbp1...@gmail.com >:
>
>> I kind of get you there adding a setting
>>
>> @string central-dock-widget = outline
>>
>> I have attached a screen shot.
>>
>
>
> However, as you can see from the two screenshots attached Leo 6.1/ 
> screenshot C - and - Leo 6.2/ screenshot D behave differently.
>
> What I would like to achieve is to get the default pane setup from 6.1 
> applied to 6.2!
>
> So far none of the suggestions work :-(
>
 
I have good news and bad news.  First, the good news  With the same @string 
as above,  I was able to drag the body and tabs panes to the new positions 
that you want.The attached image Leo version is with 6.3-devel, but I got 
the same results with 6.2-final.  This is on Windows, BTW.

The bad news is that this arrangement seems to be unstable and hard to get 
in the first place.  I could only get it after repeated dragging and 
closing/reopening the outline.  Even then, if I restarted Leo, sometimes it 
lost the arrangement and I had to reopen the outline several times and drag 
before I could restore the arrangement I wanted.  But eventually, it seemed 
to become more stable, and persist through a few restarts.

When I got this to work, it was usually as follows:

1. Rendering pane invisible.
2. Outline pane in upper left.
3. Tabs pane dragged to upper right (i.e., docked in right hand side of 
upper row).
4. Body pane across the entire bottom row.

Then *if* the body pane was draggable - and sometimes it was not - then the 
render pane would  either open up in the correct place or it could be 
dragged there.

I have to emphasize that I had to drag, experiment, reopen and restart a 
lot.  Simply deleting the .leo/db folder was not enough.

Edward will say that the positions are saved and restored by the QT 
libraries, and that Leo has no control over it.  But there other QT 
applications that have complicated pane arrangements and they don't seem to 
have this problem.  There must be some factor that we don't know about.  
Especially, the draggability of a pane shouldn't be changing from session 
to session.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/ff883b84-e9c7-4c6c-af07-6cca78213da8%40googlegroups.com.

Re: New installation log

[vitalije]

On Sunday, March 29, 2020 at 8:21:05 PM UTC+2, Matt Wilkie wrote:


> Linux can add a wrinkle with system vs user installs. User is safer in my 
> experience. Morale of a painful story I havn't shared: *never use `sudo 
> pip install`*. It can take a looong time to extricate from mixed up  
> package manager installs and pip installs in system.
>
> -matt
>
>
That's exactly why I prefer anaconda. It never  requires root privileges, 
so there is no need for doing `sudo pip install`.

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 email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/6abcbc1f-216b-47db-8f01-5dcda3f24706%40googlegroups.com.

Re: New installation log

[Matt Wilkie]

>
> PyQt5 isn't the only requirement for leo. The setup.py file (used by pip) 
> has all the requirements. Maybe these instructions would be better as it 
> would get all the dependencies and not just PyQt5:
>
> Install python3
> if not using git:
>
> pip install leo
>
> If using git:
>
> git clone 
>
> pip install --editable leo-editor
>
>
 
As of py3.6 this should always work. 

Linux can add a wrinkle with system vs user installs. User is safer in my 
experience. Morale of a painful story I havn't shared: *never use `sudo pip 
install`*. It can take a looong time to extricate from mixed up  package 
manager installs and pip installs in system.

-matt

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/3cf7b60d-b516-4cfa-8456-a08211c6bc37%40googlegroups.com.

Re: Proposed change to setup.py

[Matt Wilkie]

 

> Then you could keep your development code entirely out of the repo until 
> you got it to the point it was worth adding it in.  I'd like that.
>

A fork would accomplish this and then be easier to add to the main repo 
later. I think so anyway, but there  might be things I'm not considering 
that could make it more work than is desireable.

 

>  
>
>> Also for sde-byside it's best not to use the same HOME, as files in the 
>> .leo folder might get messed up. 
>>
>
> That's a problem that I sometimes have, not only with side-by-side.  I 
> don't like to use side-by-side anyway except for, let's say, checking that 
> something still works in a different version of Leo.  Even virtual 
> environments don't solve this, do they? 
>

Correct, virtuals don't help with this unless you also virtualize HOME 
(which is certainly possible by the way. There's a mechanism in conda and 
probably others to run scripts automatically when the env is activated.)

-matt

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/e09af8d4-3d4a-4f84-816f-10e1b30bfcf9%40googlegroups.com.

Re: Release v6.2.1

[Edward K. Ream]

On Sun, Mar 29, 2020 at 12:46 PM Matt Wilkie  wrote:

I named the branch with a "v" prefix, which I now notice has been only used
> for tags. I don't know if we can have both a branch and tag with the same
> name.
>

Not a good idea.

> Even if we can it would be confusing, so I renamed the branch and pushed
> it following this guide:
> https://multiplestates.wordpress.com/2015/02/05/rename-a-local-and-remote-branch-in-git/
>
> Hopefully I was fast enough not to screw anyone else up.
>

Looks good to me. I'll release 6.2.1 tomorrow at the earliest.

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS0kd-66PAJjRP%2BwarCDLSnQH93kNj1obgqP4zGFzbyOdA%40mail.gmail.com.

Re: Release v6.2.1

[Matt Wilkie]

On Sunday, 29 March 2020 10:36:57 UTC-7, Matt Wilkie wrote:
>
> Please create a new 6.2.1 branch, based on 6.2, not devel.
>>
>
> ok, done. I updated the version number in leoVersion.py also.
>


 I named the branch with a "v" prefix, which I now notice has been only 
used for tags. I don't know if we can have both a branch and tag with the 
same name. Even if we can it would be confusing, so I renamed the branch 
and pushed it following this guide: 
https://multiplestates.wordpress.com/2015/02/05/rename-a-local-and-remote-branch-in-git/

Hopefully I was fast enough not to screw anyone else up.

-matt

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/71b817a6-a6a3-457e-9897-a0b4f579ac77%40googlegroups.com.

Re: Release v6.2.1

[Matt Wilkie]

>
> Please create a new 6.2.1 branch, based on 6.2, not devel.
>

ok, done. I updated the version number in leoVersion.py also.

-matt

>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/09f8f3ee-e592-40e3-9f1d-49a03e131d9b%40googlegroups.com.

Re: New installation log

[Brian Theado]

On Sun, Mar 29, 2020 at 6:09 AM Edward K. Ream  wrote:
[...]

> I am seriously considering ignoring Anaconda and miniconda in Leo's
> installation instructions:
>
> Install python 3
> (ubuntu) apt-get install pip3
> pip install PyQt5
> (optional, if not using git) pip install leo
>

PyQt5 isn't the only requirement for leo. The setup.py file (used by pip)
has all the requirements. Maybe these instructions would be better as it
would get all the dependencies and not just PyQt5:

Install python3
if not using git:

pip install leo

If using git:

git clone 

pip install --editable leo-editor


I haven't personally tested these steps recently, but have done so at one
time or another (using virtual environment).

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAO5X8CwJQN2eHJ8ExABTBwGFJ3r7_c%3DnBy5FCeE%2BWvORvB7U8Q%40mail.gmail.com.

Re: Leo's legacy layout is now the default in version 6.2

[Edward K. Ream]

On Sun, Mar 29, 2020 at 8:09 AM Thomas Passin  wrote:

> I kind of get you there adding a setting
>
> @string central-dock-widget = outline
>
> I have attached a screen shot.
>

Thanks for your help.

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS3xbpUDg_TbGDRTjgxAcvgtdN6aYe2X44xLfm2HA0NLpA%40mail.gmail.com.

Re: Proposed change to setup.py

[Thomas Passin]

On Sunday, March 29, 2020 at 12:34:56 AM UTC-4, Matt Wilkie wrote:
>
> So if I had a clone at d:\leo-clone, I'd use the following?
>>
>> python -m pip install --editable d:\leo-clone
>>
>  
> Yes.
>
> I  have been setting PYTHONPATH to d:\leo-clone.  This has always seemed 
>> to work well, as long as the dependencies have been installed in my main 
>> Python install (because of a previous Leo install, for example).  This way, 
>> I can always switch back to using the previous install just by launching 
>> from another terminal without setting PYTHONPATH.
>>
>
> If your diferent versions are in the same SCM repo (eg. hg, git) then 
> resettng to or checking out your desired version can be done without 
> messing with PYTHONPATH. This is the primary benefit of editable install, 
> it always uses what's in that directory tree *right now, *allowing you to 
> test code changes immediately.
>
> pip install -e d:\leo-clone
> pushd d:\leo-clone
> git checkout v6.1
> python -m leo.core.runLeo
> # hack, hack. do stuff in Leo 6.1. exit.
> git checkout v6.2
> python -m leo.core.runLeo
> # hack, hack. do stuff in Leo 6.2. exit.
> ...etc
>

You get the same result if you point PYTHONPATH to the clone location.  
 

> If you want to run different versions of Leo side by side then *don't *pip 
> install Leo at all, editable or not, and set PYTHONPATH the way you have 
> been. I think it's cleaner to not to change PYTHONPATH though and to use 
> `python d:\leo-clone-2\launchLeo.py` for starting. (It might mess with some 
> imports or make them unpredictable as they search in Leo's tree instead of 
> the real python tree.)
>

Yes, that's a problem because Leo plugins aren't found the same way as 
ordinary imports.  I've been thinking of asking for a change so that the 
plugins are found using the PYTHONPATH instead of the current method.  Then 
you could keep your development code entirely out of the repo until you got 
it to the point it was worth adding it in.  I'd like that.
 

> Also for sde-byside it's best not to use the same HOME, as files in the 
> .leo folder might get messed up. 
>

That's a problem that I sometimes have, not only with side-by-side.  I 
don't like to use side-by-side anyway except for, let's say, checking that 
something still works in a different version of Leo.  Even virtual 
environments don't solve this, do they? 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/9c5422b1-adef-4bc7-8ff3-54f01e49ddd7%40googlegroups.com.

Re: Leo's legacy layout is now the default in version 6.2

[Thomas Passin]

I kind of get you there adding a setting

@string central-dock-widget = outline

I have attached a screen shot.

BTW, you can add this setting just to one outline, so you can experiment 
with changing the setting(s) by closing the outline and reloading it, 
rather than needing to restart Leo each time.

The first time I tried this, the rendering pane seemed to be stuck across 
the whole bottom and was not movable.  I deleted the setting and reloaded, 
then restored the setting and reloaded again, and this time the rendering 
pane was able to share the bottom row with the tabs pane.  I'm moderately 
sure that if I had deleted Leo's db directory, I wouldn't have had the 
initial problem.

The detail that the left edges of the tabs and body panes line up is not 
automatic.  The tabs and rendering panes share the bottom row, and you can 
move the divider between them.  The body and outline share the top row, and 
you can independently move their divider.

When you move one of the panes, for example the tabs to the bottom right, 
it can be very hard to find the spot to drop it.  Sometimes the drop target 
can be tiny.  Keep moving around with the mouse and look for any tiny area 
that changes color, and you should eventually find it.

I hope this gives you what you are after.

On Sunday, March 29, 2020 at 6:16:53 AM UTC-4, Edward K. Ream wrote:
>
> On Sun, Mar 29, 2020 at 4:29 AM Viktor Ransmayr  > wrote:
>
> > This morning I tried in every possible way to achieve the pane setting 
> I'd like to have, i.e.
>
> My apologies for the troubles you are having. Can anyone give specific 
> advice.
>
> In general, it's a good idea to remove the contents of ~/.leo/db when 
> modifying layouts. You can also try to using the --init-docks command-line 
> option. Another thing to consider is making something other than the 
> outline the so-called central widget.  You might try @string 
> central-dock-widget = body.
>
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/76a8d6fd-ff88-410f-9c41-bbb7f6286e23%40googlegroups.com.

Re: New installation log

[Edward K. Ream]

On Sun, Mar 29, 2020 at 6:01 AM vitalije  wrote:

> I use anaconda on all my computers, but I install packages using `pip
> install`not `conda`. I also don't create nor use any conda environments.
>
> I like the fact that anaconda is installed, by default, in my home folder.
> So, installing packages doesn't require root privileges. The only trouble I
> sometimes have is that some programs rely on /usr/bin/python and not on
> python found in the PATH (which is anaconda python).
>

Thanks for these comments. I'm not ever going to dissuade people from using
Anaconda, but I'm not sure the present encouragement is all that helpful.

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS0TAQ25AVRsT7vJr-iZGmFD6GGC3YOF%3DwtwNSmE6_FoHw%40mail.gmail.com.

Re: New installation log

[vitalije]

I use anaconda on all my computers, but I install packages using `pip 
install`not `conda`. I also don't create nor use any conda environments.

I like the fact that anaconda is installed, by default, in my home folder. 
So, installing packages doesn't require root privileges. The only trouble I 
sometimes have is that some programs rely on /usr/bin/python and not on 
python found in the PATH (which is anaconda python).

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 email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/24108a5a-22ae-4faa-8e7c-7b5e081f5271%40googlegroups.com.

Re: Profiling tree.full_redraw

[Edward K. Ream]

On Sat, Mar 28, 2020 at 4:42 AM vitalije  wrote:

> This morning I wrote a small script to profile full_redraw method. [snip]
>

g.toUnicodeFileEncoding was called 2504395 times during the exection of my
script?! os.path.normpath was called 1128328 times.

I have just created #1548
 for this.

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS2MkJwFof5GDY%2BZ5vyRjSp5KkSQk-UXDKX2c4itL60yhg%40mail.gmail.com.

Re: Release v6.2.1

[Edward K. Ream]

On Sun, Mar 29, 2020 at 1:02 AM Matt Wilkie  wrote:

> Edward,
>
> Commit 77f4000d re-adds MANIFEST.in to git exports and releases and is the
> fix for #1547 and #1512, the inability for pip install to work from zip
> release archives. It's worthy of a new dot release. I committed to devel
> before remembering there's a new release branch workflow.
>

Please create a new 6.2.1 branch, based on 6.2, not devel.

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS0xDPRDBgEoSgdsL3Sx2fi3%3Dfg03fPxN2KUbmfRQSGXDg%40mail.gmail.com.

Re: Leo's legacy layout is now the default in version 6.2

[Edward K. Ream]

On Sun, Mar 29, 2020 at 4:29 AM Viktor Ransmayr 
wrote:

> This morning I tried in every possible way to achieve the pane setting
I'd like to have, i.e.

My apologies for the troubles you are having. Can anyone give specific
advice.

In general, it's a good idea to remove the contents of ~/.leo/db when
modifying layouts. You can also try to using the --init-docks command-line
option. Another thing to consider is making something other than the
outline the so-called central widget.  You might try @string
central-dock-widget = body.

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS19Pv3nxuNXBtLO%3D75qpea%3DBCHTw2jPMBqtxKzDdLCYAw%40mail.gmail.com.

Re: New installation log

[Edward K. Ream]

On Saturday, March 28, 2020 at 9:00:14 AM UTC-5, Edward K. Ream wrote:

> It's easy to install python using an executable installer and `pip 
install PyQt5`.

Installation is *simple *because at each step it's clear what to install 
next. That's because of various console messages within Leo.

In other words, it's quite possible to install the prerequisites for Leo 
without having to remember anything, except maybe the line above.

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/db10ac1c-929d-4566-9026-1327649c4026%40googlegroups.com.

Re: New installation log

[Edward K. Ream]

On Sat, Mar 28, 2020 at 11:13 PM Matt Wilkie  wrote:

If you install Leo (or whatever) into the base environment instead of
> creating a distinct envs for projects you can get the simplicity of a
> single system environment, similar to installing python the regular way,
> and still use the conda package manager (if that's a desirable thing for
> your work).
>
> In this case add the base env bin to PATH so it's always available or use
> the system menu 'Anaconda Prompt' (which is the same as `activate` with no
> env specified).
>
> It should be noted this goes against the grain of Anaconda's design and
> they recommend against it. Still works though!
>

Thanks for these comments. Imo, Anaconda has become harder to use in the
last year or so. Not sure why.

*Aha*: Now that Leo requires python 3, we can assume pip is always
available. (Actually, people may have to use apt-get on Linux to get pip3.)
In my recent experience, pip is easier to use and more solid than conda.
Ymmv.

I am seriously considering ignoring Anaconda and miniconda in Leo's
installation instructions:

Install python 3
(ubuntu) apt-get install pip3
pip install PyQt5
(optional, if not using git) pip install leo

And that's it. Comments?

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS339qXkd%3DDeYWOWnE3g4o%3Dy_kP0zMYke3OK%3DmhzUtX6wA%40mail.gmail.com.

Re: Viewrendered3 Read For Beta Testing

[Edward K. Ream]

On Sat, Mar 28, 2020 at 11:13 PM lewis  wrote:

> I do have nbformat installed.
> Since build eb6f4ec070 I get this in console log:
> --
> Empty setting name in False
> set parent @settings
> Leo 6.3-devel, devel branch, build eb6f4ec070
> 2020-03-28 18:58:09 -0500
> VR3: *** No Markdown ***
> VR3: *** No nbformat
> [snip]
>
> However I do not get that message in Leo's log pane. Why are there extra
> messages in the console log about Markdown and nbformat?
>

Thomas and I are actively working on vr3. These messages are for debugging.
They will likely change in the near future.

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS2YFxjv2cntgQd0nDH_%3DtQ2Die%2BH_7EtaYoELQxV3romA%40mail.gmail.com.

Re: Leo's legacy layout is now the default in version 6.2

[Viktor Ransmayr]

Hello Edward, Matt & Thomas,

Am Sa., 28. März 2020 um 23:06 Uhr schrieb Viktor Ransmayr <
viktor.ransm...@gmail.com>:

> Hello Matt,
>
> Am Sa., 28. März 2020 um 22:08 Uhr schrieb Matt Wilkie :
>
>> Let's try that again:
>> https://leoeditor.com/FAQ.html#how-can-i-arrange-qt-docks
>>
>> On Saturday, 28 March 2020 14:08:27 UTC-7, Matt Wilkie wrote:
>>>
>>> Viktor,
>>>
>>> Thomas Passin contributed his recipe to the FAQ which mightbe helpful:
>>>
>>
> Thanks a lot. - I'll try the recipe tomorrow ...
>

This morning I tried in every possible way to achieve the pane setting I'd
like to have, i.e.

* 'Outline [1/1]'  plus 'Tabs [1/2]' to the right
* 'Body [2/1]' below Outline &  'Render [2/2]' to the right of Body & below
Tabs ...

As recommended by Edward I start Leo with --use-docks - and - as suggested
by Matt & documented by Thomas in the FAQs, I experimented with

* @string central-dock-widget = body or outline - as well as -
* @string initial-split-orientation = horizontal or vertical
* and deleted ~/.leo/DB

Unfortunately without success.

Has anyone succeeded with this recipe & 'Leo 6.2 final'?

With kind regards,

Viktor

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAAeSrGKMwz10PF0RyfAjfhX2zxKBGbf7SFyLXOHOvxbmeRJhpQ%40mail.gmail.com.

Release v6.2.1

[Matt Wilkie]

Edward, 

Commit 77f4000d re-adds MANIFEST.in to git exports and releases and is the 
fix for #1547 and #1512, the inability for pip install to work from zip 
release archives. It's worthy of a new dot release. I committed to devel 
before remembering there's a new release branch workflow.

Should I commit this straight to v6.2 branch or create a new v6.2.1 branch 
from v6.2 and then commit? (or something else)

-matt

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/fa428593-493f-4c2e-9246-ab96b4234225%40googlegroups.com.