Re: how should an (ordinary) user install Leo on Linux?

On Mon, 27 Nov 2017 13:05:48 -0500 Offray Vladimir Luna Cárdenas wrote: > Hi, > > I could try to install Leo on Linux via miniconda. There is any > channel I need to add for that? My actual installation doesn't find > Leo (see result below) Ok, kind of funny - there's no

Re: how should an (ordinary) user install Leo on Linux?

Hi, I could try to install Leo on Linux via miniconda. There is any channel I need to add for that? My actual installation doesn't find Leo (see result below) conda install leo Fetching package metadata . PackageNotFoundError: Packages missing in current channels:  

Re: how should an (ordinary) user install Leo on Linux?

To clarify my concern about Anaconda installs directing people away from Leo, here's what the Anaconda navigator looks like: https://docs.anaconda.com/_images/navigator-home-1-6.png If you're trying to install Leo and see that Spyder button - meh, close enough, what do I care what it's called?

Re: how should an (ordinary) user install Leo on Linux?

On Mon, 27 Nov 2017 12:24:31 -0500 Offray Vladimir Luna Cárdenas wrote: > On 27/11/17 11:24, Terry Brown wrote: > > On Mon, 27 Nov 2017 06:54:03 -0800 > > Chris George wrote: > > > >> Installing Anaconda just works. > > In the list of installation

Re: how should an (ordinary) user install Leo on Linux?

On 27/11/17 11:24, Terry Brown wrote: > On Mon, 27 Nov 2017 06:54:03 -0800 > Chris George wrote: > >> Installing Anaconda just works. > In the list of installation options, we could maybe characterize them > in a few words, e.g. for Anaconda, "larger download, but this is

Re: how should an (ordinary) user install Leo on Linux?

On Mon, Nov 27, 2017 at 9:59 AM, brobr wrote: > ​Leo is an app, not a python package. >> > > Well I do not think this is a relevant difference; all pip-installs end in > python/site-packages. And most setup.py installs as well. > ​Yes. I was mistaken. Edward -- You

Re: how should an (ordinary) user install Leo on Linux?

On Mon, 27 Nov 2017 06:54:03 -0800 Chris George wrote: > Installing Anaconda just works. In the list of installation options, we could maybe characterize them in a few words, e.g. for Anaconda, "larger download, but this is the option that 'just works'". Cheers -Terry --

Re: how should an (ordinary) user install Leo on Linux?

> > ​Leo is an app, not a python package. > Well I do not think this is a relevant difference; all pip-installs end in python/site-packages. And most setup.py installs as well. Leo is quite big, > 30 Mb; for comparison, numpy is 15 Mb, pylint ~2.3 Mb, pyenchant ~0.4 Mb and all sit in the

Re: how should an (ordinary) user install Leo on Linux?

I not a programmer either. Installing Miniconda is the same effort as installing Anaconda, gives you the same core functionality (with less overheat and preinstalled packages, mostly for science) and it saves bandwidth, space *and* time, which is handy in places in the Global South, where

Re: how should an (ordinary) user install Leo on Linux?

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

Re: how should an (ordinary) user install Leo on Linux?

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

Re: how should an (ordinary) user install Leo on Linux?

On Mon, Nov 27, 2017 at 6:12 AM, Edward K. Ream wrote: > On Sun, Nov 26, 2017 at 12:56 PM, wrote: > > > 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

Re: how should an (ordinary) user install Leo on Linux?

On Sun, Nov 26, 2017 at 12:56 PM, wrote: > I think that the suggested method of installing anaconda is not the > optimal way to facilitate this; > ​I mostly disagree, as I have just explained in another reply. 5) a setup.py is the standard way of installing a python program

Re: how should an (ordinary) user install Leo on Linux?

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

Re: how should an (ordinary) user install Leo on Linux?

a mime-type will be welcome, thank you ​ -- 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

Re: how should an (ordinary) user install Leo on Linux?

I figured out how to create a new mime type for Leo, which is a prerequisite for the file association in Linux. will post my solution here soon. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving

Re: how should an (ordinary) user install Leo on Linux?

> With regard to dependencies, do you recall what docutils, pyxml, and > pyenchant required for? I don't have them in my list, but haven't > seen any errors about them either. > Nevermind, answered a couple myself, and am starting new thread to collect all dependencies Matt -- You received

Re: how should an (ordinary) user install Leo on Linux?

Thanks for the recipe Chris. Steps 2 & 3 are about to get a whole lot easier, pending resolution of issue # 586 which I'm nearing the end of. With regard to dependencies, do you recall what docutils, pyxml, and pyenchant required for? I don't have them in my list, but haven't seen any errors

Re: how should an (ordinary) user install Leo on Linux?

I never use viewrendered except to read about plugins. :-) Chris On Wed, Nov 22, 2017 at 9:02 AM, Josef wrote: > > >> 2. Install the prerequisites for Leo. These I usually install using pip >> or the package manager in the distribution. Try pip first. >> >> docutils, pandoc,

Re: how should an (ordinary) user install Leo on Linux?

> > 2. Install the prerequisites for Leo. These I usually install using pip or > the package manager in the distribution. Try pip first. > > docutils, pandoc, pyxml, pyenchant, git > > thank you for the tip. Installing docutils seems to have fixed my problem with the viewrendered plugin. -

Re: how should an (ordinary) user install Leo on Linux?

Hi Chris, thanks for the tips. In fact, I have installed Leo in a pretty similar way as you (and I also use Leo already for several years). My problem was the file association, which you avoided. Also, for a while I was not able to use the viewrendered plugin any more, and I am surprised you

Re: how should an (ordinary) user install Leo on Linux?

Hello Josef, I am a writer and a longtime Linux Mint user. I recently switched to Chakra as Mint dropped KDE. I am not a programmer. I have been using Leo for ten years as my primary editor. (Wow, time flies). Here is how I install Leo. 1. Install the latest Anaconda from here: