On Sat, Jun 5, 2021 at 4:23 PM Félix wrote:
> I've come to the conclusion that the server.py script (and its
> client/test scripts) should go back to their original location:
> /leo/core so that anyone has them regardless of the
> installation method that was used to install Leo.
I'm good with
Thanks to David, Edward, Victor and others participating in this particular
thread about server script file location,
To conclude and move forward with this specific (and important) issue that
Victor raised:
I tough about this in the last few days and I've come to the conclusion
that the
On Thursday, May 20, 2021 at 1:39:06 PM UTC-4 tbp1...@gmail.com wrote:
> In my view, Leo *is* a 3rd party python package and should be installable
> via pip. It is true that some Linux systems will tinker with the
> directories, paths, etc and want you to install certain packages using
>
Thank you Viktor for those enlightening facts. Much appreciated input!
--
BTW Edward, please feel free to move leoserver.py and leoclient.py inside
the /leo/ folder. Its not too bad still somewhat easy to browse too, for
users setting up a remote client like leointeg.
(It's still easier than
Hello Félix, hello Edward,
Félix schrieb am Freitag, 21. Mai 2021 um 04:05:14 UTC+2:
>
> Now something that popped in my mind a second ago is intriguing me very
> much: If someone had installed Leo with pip, would then it be possible for
> that person to just start Leo, open leopyref.leo, hit
On Thu, May 20, 2021 at 9:05 PM Félix wrote:
> If someone had installed Leo with pip, would then it be possible for that
person to just start Leo, open leopyref.leo, hit ctrl+s, and have
launchLeo.py , flake8-leo.py, launchLeo-console.py, etc. be generated in
their root Leo installation folder?
I don't think that you would want it to work exactly this way because that
would change the action of the CTRL-S command and that would be confusing.
Instead, how about a button for leoPyRef that would do those things?
On Thursday, May 20, 2021 at 10:05:14 PM UTC-4 Félix wrote:
> First of
First of all, thank you very much tbp1, for answering questions regarding
the installation of Leo, and to shed some light on this matter.
Now something that popped in my mind a second ago is intriguing me very
much: If someone had installed Leo with pip, would then it be possible for
that
In my view, Leo *is* a 3rd party python package and should be installable
via pip. It is true that some Linux systems will tinker with the
directories, paths, etc and want you to install certain packages using
their own package manager. But Leo as a project can't cater to all these
possible
What happened to the standard 'installer' program concept... "install.msi"
or .exe. or whatever? Is that still a thing?
Leo is not a python library like 'websockets' or some other 3rd party
functionality library... should it not be installed with a 'real'
installation program? (on windows)
On Tuesday, May 18, 2021 at 3:32:23 AM UTC-5 viktor@gmail.com wrote:
> They [the files in leo-editor folder] don't exist at all, if the user
has installed Leo via pip from PyPI - and - not via 'git clone' from GitHub.
Somehow I never understood this.
> The problem / surprise occurs for
Thank you Viktor!
(glad I asked you - this was mystifying for me!)
--
Félix
On Tuesday, May 18, 2021 at 4:32:23 AM UTC-4 viktor@gmail.com wrote:
> Hello Félix
>
> Félix schrieb am Dienstag, 18. Mai 2021 um 00:55:18 UTC+2:
>
>>
>> I don't know much at all about those python system specific
Hello Félix
Félix schrieb am Dienstag, 18. Mai 2021 um 00:55:18 UTC+2:
>
> I don't know much at all about those python system specific issues.
> (although I wonder how the other python files that import parts of leo do
> exist in the root of the leo folder without problem, such as
No biggie :)
I'll just add a little text 'tip' that hints that the leoserver.py is just
inside the '/leo' subfolder of the main Leo installation folder...
I don't know much at all about those python system specific issues.
(although I wonder how the other python files that import parts of leo
On Sun, May 16, 2021 at 2:21 AM Viktor Ransmayr
wrote:
> Hello Edward & Félix,
>
> Looking into the sources I also noticed, that we'll run into a similar
> problem as already documented in issue #603.
>
> In other words, both files should be moved from the top-level, i.e.
>
Thanks for this.
Hello Edward & Félix,
Looking into the sources I also noticed, that we'll run into a similar
problem as already documented in issue #603.
In other words, both files should be moved from the top-level, i.e.
* https://github.com/leo-editor/leo-editor/blob/devel/leoserver.py
*
16 matches
Mail list logo
