Re: How did I came across Leo?

On Saturday, March 3, 2018 at 2:39:59 AM UTC-5, Edward K. Ream wrote: > > On Fri, Mar 2, 2018 at 11:39 PM, David Szent-Györgyi > wrote: > >> I employed Leo for an oddball use case, which it addressed beautifully. >> > > ​ > Quite an interesting project. Your post is now in

Re: The first, urgent task: show people what Leo already has

> > > ​> ​ > If the Python console should be used, make it visible in the menu; don't > bury it in the documentation. > > ​Actually, my intention is to make key features visible *directly*, not > just in menus.​ > > I am going to enable the python_terminal plugin today, in both master and >

Re: I love Leo, but... Scrivener and Org-Mode

On Saturday, March 3, 2018 at 7:50:31 AM UTC-5, Israel Hands wrote: > > What do I use Leo for then? > > Content - for me content is king. Manipulate it - tag it - filter it - > anything you like but it's about content. > > So my first use of Leo is as a free form database for notes, minutes, >

Re: python_terminal.py now enabled by default in master & devel

On Sat, Mar 3, 2018 at 10:04 AM, Edward K. Ream wrote: This plugin creates a python terminal in the Log pane. > ​It may be possible to use an ipython terminal instead. This will always be optional I am excited about the possibilities: better syntax coloring, better

Re: The first, urgent task: show people what Leo already has

On Sat, Mar 3, 2018 at 12:47 AM, rengel wrote: ​> ​ you might want to study the user interface of PyCharm ( https://www.jetbrains.com/pycharm/), especially their wording of menu entries and their 'Tools' menu. ​Good idea. It's on my list of things to do

I love Leo, but... Scrivener and Org-Mode

Disclaimer - I understand that nothing breaks software like trying to satisfy the demands of disparate individual users. I do realise that so this is observation not really requests and certainly not criticism! Leo is wonderful. When I read the group postings I often don't feel at all like the

Re: I love Leo, but... Scrivener and Org-Mode

On Saturday, March 3, 2018 at 8:16:33 AM UTC-5, Edward K. Ream wrote: > ​#774 Convert Leo trees to LaTex as in Scrivener > is a new > enhancement request. > > Googling "scrivener convert to LaTeX" yields this page >

Re: Terry, please update leo_edit_pane branch in branches.md

On Sat, 3 Mar 2018 01:18:08 -0600 "Edward K. Ream" wrote: > ​I see. Is there any reason to retain leo_edit_pane? If there is, > please update branches.md. If not, please delete the branch :-) Gone. Cheers -Terry -- You received this message because you are subscribed

Re: Is it time to discuss Leo in a MacInTouch lovefest for Dave Winer's MORE outliner?

On Sat, Mar 3, 2018 at 10:00 AM, David Szent-Györgyi wrote: > ​ ​ I recall reading that MORE was one of Edward's inspirations for Leo. It was. Clones would not have happened otherwise. > ​ ​ A MacInTouch discussion of reminiscences of old technology is full of praise for

Re: Terry, please update leo_edit_pane branch in branches.md

On Sat, Mar 3, 2018 at 11:23 AM, Terry Brown wrote: > > Is there any reason not to create an issue for this? > No, I should probably do that to clarify current subtasks. Please do. ​Imo it's​ the ​best​ way to keep up with major projects like this. > I guess recent work

Re: Rethinking Leo's distribution process

On Thursday, March 1, 2018 at 12:49:48 PM UTC-5, Edward K. Ream wrote: > > On Thu, Mar 1, 2018 at 11:11 AM, Matt Wilkie > wrote: > >> >> - No need for sourceforge, pyinstaller, windows installer. >>> >> >> The only significant advantage of those installers over the pip install

python_terminal.py now enabled by default in master & devel

This plugin creates a python terminal in the Log pane. 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 post to

Re: I love Leo, but... Scrivener and Org-Mode

On Sat, Mar 3, 2018 at 8:34 AM, David Szent-Györgyi wrote: Googling "scrivener convert to LaTeX" yields this page >> . >> It doesn't look to difficult to translate this approach into Leo. I've >> given

Nightly builds will continue

I see no great reason to change anything about nightly builds. Some people may use them. If not, no great harm is done. Using the devel branch instead of master for most work implicitly changes what the nightly builds represent. Previously, they were the bleeding edge. Now, they are

Re: Terry, please update leo_edit_pane branch in branches.md

On Sat, 3 Mar 2018 10:43:35 -0600 "Edward K. Ream" wrote: > ​Thanks. Where would I find documentation for what you did? Not that it's a reason not to document as I go, but the project's far from finished. It aspires to replace: - viewrendered* - the body pane (with,

Re: The first, urgent task: show people what Leo already has

On Sat, Mar 3, 2018 at 8:24 AM, Zoom.Quiet wrote: ​>​ > 1. Better theme setting and pre-built themes > suggest base Sublime Text 3 's ​ ​ Spacegray/base16-eighties.dark.tmTheme -> predawn-DEV.sublime-theme ​Thanks. ​ I've made a note of this suggestion in #766. ​Edward​

Re: The first, urgent task: show people what Leo already has

On Sat, Mar 3, 2018 at 8:24 AM, Zoom.Quiet wrote: > > 1. Better theme setting and pre-built themes ​ ​ #766 > this is the biggest profit task; ​Just to underscore how wretched the present situation is, it took about 10 minutes for me to figure out how to enable Chris

Re: Mermaid flowcharts from Leo subtree in Leo Vue

Offray, Wanted to respond this before but didn't have time. About the name, Leo Web makes sense in that the LeoVue project shows the power of the web dev ecosystem. However, for a couple of reasons I think LeoVue is still the better name: 1. LeoVue isn't Leo, it is a content viewer, not a

Re: How did I came across Leo?

On Sat, Mar 3, 2018 at 6:49 AM, David Szent-Györgyi wrote: ​> ​ My coworker's motto was, "If it's stupid, and it works, it isn't stupid"! ​Hehe. It's an arguable point.​ ​There is also an argument for cleanups, when possible.​ ​ Vitalije is working on collapsing Leo's

Re: Rethinking Leo's distribution process

On Saturday, March 3, 2018 at 9:06:12 AM UTC-5, Edward K. Ream wrote: > > > ​I would happily abandon all the work we have done, except perhaps > assoc.exe. > Unless I misread the current situation, the NSIS installer for Leo and all its files is no longer in use - the file association is all

Is it time to discuss Leo in a MacInTouch lovefest for Dave Winer's MORE outliner?

I recall reading that MORE was one of Edward's inspirations for Leo. A MacInTouch discussion of reminiscences of old technology is full of praise for MORE's technology, starting with this comment . -- You received

Re: Rethinking Leo's distribution process

On Sat, Mar 3, 2018 at 7:44 AM, David Szent-Györgyi wrote: > A decade ago, when you were kindly using NSIS to generate proper Windows > installers for each release of Leo, I worked on an enhanced NSIS installer. > ​I would happily abandon all the work we have done, except

Re: Rethinking Leo's distribution process

On Sat, Mar 3, 2018 at 7:41 AM, David Szent-Györgyi wrote: > > I can't find assoc.exe in the source code for Leo. Where is it? What does > it do? > ​leoDist.leo#NSIS source files-->@file ../../leo_assoc.nsi​ ​It sets Windows associations without installing files. Edward --

Re: The first, urgent task: show people what Leo already has

On Friday, March 2, 2018 at 11:27:59 AM UTC-5, Edward K. Ream wrote: *2. Better support for markdown* > > #767: Add markdown command similar to rst3 command > . I want to move > Leo's docs to markdown. > > #763: Use html comments to support

Re: Terry, please update leo_edit_pane branch in branches.md

On Sat, Mar 3, 2018 at 10:52 AM, Terry Brown wrote: Not that it's a reason not to document as I go, but the project's far > from finished. It aspires to replace: > ​ [snip] > ​Is there any reason not to create an issue for this? I'm confused. Why delete the branch if

Re: Terry, please update leo_edit_pane branch in branches.md

On Sat, 3 Mar 2018 10:58:28 -0600 "Edward K. Ream" wrote: > On Sat, Mar 3, 2018 at 10:52 AM, Terry Brown > wrote: > > Not that it's a reason not to document as I go, but the project's far > > from finished. It aspires to replace: > > ​ [snip] > >

Re: The first, urgent task: show people what Leo already has

On Sat, 3 Mar 2018 11:40:28 -0600 "Edward K. Ream" wrote: > Leo *must* have a library of pre-built themes that users can choose > without knowing *anything* about @settings trees and > myLeoSettings.leo. This sounds like a good idea - I just want to point out that the

Re: leovue meets leo4sqlite

I fixed the handling of docstrings (at least the multiline ones) I put a demo on the leo-examples repo: See https://kaleguy.github.io/leo-examples/leo4sqlite/#/t/5-26/ The latter page shows that the docstring is being properly formatted for the web. To get this to work with your version, just

Re: I love Leo, but... Scrivener and Org-Mode

On Sat, Mar 3, 2018 at 6:50 AM, Israel Hands wrote: ​> ​ Disclaimer ​No need for that. ​> ​ ​ Scrivener ​.. ​ has a relatively simple 'compile' mode to Latex. ​#774 Convert Leo trees to LaTex as in Scrivener is a new

Re: How did I came across Leo?

On Saturday, March 3, 2018 at 7:56:48 AM UTC-5, Edward K. Ream wrote: > > On Sat, Mar 3, 2018 at 6:49 AM, David Szent-Györgyi > wrote: > > ​> ​ > My coworker's motto was, "If it's stupid, and it works, it isn't stupid"! > > ​Hehe. It's an arguable point.​ > > ​There is also

Re: Rethinking Leo's distribution process

A decade ago, when you were kindly using NSIS to generate proper Windows installers for each release of Leo, I worked on an enhanced NSIS installer. In those days, it was possible to install Python itself for all users of a machine or for the current user only, and I figured out how to handle

Re: Terry, please update leo_edit_pane branch in branches.md

On Sat, Mar 3, 2018 at 10:39 AM, Terry Brown wrote: ​> ​ > ​Is there any reason to retain leo_edit_pane? ...​If not, please delete the branch. > Gone. ​Thanks. Where would I find documentation for what you did? Edward -- You received this message because you are

Re: The first, urgent task: show people what Leo already has

On Sat, Mar 3, 2018 at 9:45 AM, rengel wrote: >> the python_terminal plugin ​[is now]​ visible in the plugins menu and in the Log pane. > Does this imply that every outline opened has its own Python console? ​At present, the answer is yes. A global console is

Re: leovue meets leo4sqlite

I've had my own difficulties but the site is back up. I will be making the suggested updates, thanks. tscv11 -- 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

Re: I love Leo, but... Scrivener and Org-Mode

Wow, reading Israel's post made me me think I wrote it (except the org-mode part). Probably 80+% of my work in Leo is writing content w/ LaTEX output. Most of the rest is variations of markdown and RST. I tried moving my work to Scrivener and really like it a lot. However, I like Leo better

Re: leovue meets leo4sqlite

It's clear that I need to keep better track of this google group. I must have turned off email notifications because I had no idea anyone was communicating with me. My apologies - I'll fix that. If I have an active Leo project I think I should keep tabs on what's happening here, so I will make

Re: leovue meets leo4sqlite

Just realized there is a bug in the bookmarks for subtrees. So the 5-26 link goes just to node 5 and the 4-23 links to node 4. 5-26 is supposed to go the = leo4sqlite script = / << docstring >> You'll see that the version in the link below has the correct formatting. 4-23 points to the Sqlite3

Re: The first, urgent task: show people what Leo already has

On Sat, Mar 3, 2018 at 11:55 AM, Terry Brown wrote: > ​​ I just want to point out that the ​ ​ problem identified here is @settings / myLeoSettings.leo / using Leo as a settings manager, and not the theme generation machinery per se. I have just spent all afternoon

Re: The first, urgent task: show people what Leo already has

On Fri, Mar 2, 2018 at 9:24 PM, lewis wrote: A recent discussion by Terry of the valuespace plugin helped me grasp just > one basic idea of what it did. > Terry noted "The vs-eval-block command from the valuespace plugin gives > Leo a cell like behavior." This seems to