I am not a programmer. I can't emphasize that enough.
I am a writer who has been using Leo for the past decade. I am also a Linux user. Over the years I have used Debian, Ubuntu, Arch, Mandrake, Mint and now Chakra. I have gone through several desktop computers and a number of laptops. Along the way I have learned a few things about Linux distributions, python and Leo. As bandwidth and hard drive space are far cheaper than my time, I settled on using Anaconda to keep me out of the morass of spending hours troubleshooting how different distributions deal with python. It may have prevented me from learning more about python and achieving the most precise and streamlined python install possible for my needs, but it has certainly saved me a LOT of time that I have been able to spend writing. Installing Anaconda just works. Chris On Mon, Nov 27, 2017 at 5:29 AM, Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: > Hi, > > Anaconda can be overkill for installing Leo, but Miniconda is no (only 60 > mb). It's the preferred way those days to give installing support in the > Python (scientific) ecosystem, and making Leo conda installable is > important for the same reasons that Jupyter, Numpy and all the other > packages in that ecosystem have chosen coda: to make installation easier > and more modular and let you experiment without system specific installs > that preclude parallel versions and sandboxing and are distro/OS specific. > > So a good install procedure for Leo could be: > > - Install *miniconda* (60 mb). > > - conda install leo. > > A template of how this is done in Jupyter is here: > > https://cs205uiuc.github.io/guidebook/resources/python-miniconda.html > > Cheers, > > Offray > > On 26/11/17 13:56, rvn...@tesco.net wrote: > > I think that the suggested method of installing anaconda is not the > optimal way to facilitate this; it should be python-simple: > > 1) the user does not necessarily learn what exactly gets installed on > his/her system > 2) it creates an overload in case people are not needing all included > packages (if people are not using leo for python programming and do not > need access to ipython, scipy, numpy, matplotlib etc; anaconda is overload) > 3) it bypasses the possibility of providing distribution-specific installs > which often are guided by specific guidelines > 4) the possibility of installing leo as a python program should be kept > python-KISS, that is via python-install methods like pip (which will sort > out required dependencies) or setup.py > 5) a setup.py is the standard way of installing a python program and used > by distribution-specific install-scripts that enable keeping track of what > is installed. Pip makes this more obscure so that it is important that a > setup.py file is present and up-to-date > > What is important is that configuration on a linux system can become more > straightforward than it currently is, that is via use of the leoSettings. > For example, all menu-related settings to open a file using another editor > is windows-specific. This can be changed, as I am learning now, by copying > the @settings/Menu/Open With-node from leoSettings.leo to myLeoSettings.leo > file and overwrite the windows-specific bits with linux specific > paths/executables. But it would be helpful if not each linux user has to do > this for him/her self. This has been picked up and is addressed in > leo-editor/issues/596 > <https://github.com/leo-editor/leo-editor/issues/596> > > The mime-type script is interesting; thanks. I found full instructions for > applying this here: www.freedesktop.org/..AddingMIMETutor/ > <https://www.freedesktop.org/wiki/Specifications/AddingMIMETutor/> . > Together with a .desktop file, this could be a nice addition as part of the > leo distribution and then, together with the leo.desktop file (like > attached) being installed by the distribution according to its own > guidelines. > > PS I am on Slackware linux where we use for each application a script (a > so called SlackBuild) to compile and install the program; this enables > maintainers to copy files to particular places when needed (like the > leo.desktop to /usr/share/applications and leo.mime to > /usr/share/mime/packages). The currently used version is on > https://slackbuilds.org/repository/14.2/development/leo/ > > > cheers, > > rob > -- > 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 post to this group, send email to leo-editor@googlegroups.com. > Visit this group at https://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. > > > -- > 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 post to this group, send email to leo-editor@googlegroups.com. > Visit this group at https://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. > -- 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
