On Monday, April 20, 2020 at 1:23:07 AM UTC-4, Matt Wilkie wrote:
>
>
>
>> What's more, if I set PYTHONPATH to point to my git clone location, the
>> leo command launches Leo from there instead of from the standard
>> install. Excellent - that's just what I would want.
>>
>
> Cool, I didn't
> What's more, if I set PYTHONPATH to point to my git clone location, the
> leo command launches Leo from there instead of from the standard
> install. Excellent - that's just what I would want.
>
Cool, I didn't know that.
> OTOH, I don't see a leo.exe command in the Git clone. I
On Sunday, April 19, 2020 at 8:37:38 PM UTC-4, Matt Wilkie wrote:
>
> In order for the bare command leo to work, the operating system has to
>> know that it's a Python file and that it's supposed to open a Python file
>> using Python. Sometimes this chain of identification doesn't get set up
>
> In order for the bare command leo to work, the operating system has to
> know that it's a Python file and that it's supposed to open a Python file
> using Python. Sometimes this chain of identification doesn't get set up
> right. It seems like that was the problem when you got this error
>
> thank you very much for your help. I have tried everything I could but
> everything failed. Finally, I have decided to reinstall Python and the
> recommended installation process by Matt went smoothly :).
> So maybe there was something wrong with my Python.
>
You're welcome, and thanks
In order for the bare command leo to work, the operating system has to know
that it's a Python file and that it's supposed to open a Python file using
Python. Sometimes this chain of identification doesn't get set up right.
It seems like that was the problem when you got this error message:
Since you're using powershell, setting up the git repository to use scoop
might be the simplest solution to this. Of course that needs to be done by
us so it would support scoop installs.
Tom
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To
Hello Jan,
Am So., 19. Apr. 2020 um 17:24 Uhr schrieb Iohannes <
jan.odstrci...@gmail.com>:
>
> thank you very much for your answer! I have followed your instruction.
> After some struggle (I had to change the maximal lenght of PATH of the
> filesystem), I have been able to install it. Yet, the
Dear Matt and Viktor,
thank you very much for your help. I have tried everything I could but
everything failed. Finally, I have decided to reinstall Python and the
recommended installation process by Matt went smoothly :).
So maybe there was something wrong with my Python.
I have a couple of
Hello Jan,
The most solid way is to install from sources
(https://leoeditor.com/installing.html#installing-leo-from-sources-all-platforms)
but unfortunately it's not the friendliest route for non-comandline folk.
Overview:
1. Install python (v3.6+)
2. Download Leo sources, and unpack
Dear Viktor,
thank you very much for your answer! I have followed your instruction.
After some struggle (I had to change the maximal lenght of PATH of the
filesystem), I have been able to install it. Yet, the last command gives me
an error:
PS C:\Users\HOMEDIR\PyVE\PyPI\Leo> leo --use-docks
Hello Iohannes,
Am So., 19. Apr. 2020 um 15:30 Uhr schrieb Iohannes <
jan.odstrci...@gmail.com>:
> Hi, beginner here.
>
> I would like to ask you - is there any user-friendly installer for Leo?
>
I'm not aware of any Windows-specific installer for Leo at least since
version 6.0.
I am using
12 matches
Mail list logo
