Re: How did I came across Leo?

The title of this thread made me remember when I discovered Leo: it was back in 2002 on slashdot... reading the description I just had to try it out! https://slashdot.org/story/02/08/28/1655207 I remember that evening, when I was amazed at the simple outline navigation and editing inspired

Re: How did I came across Leo?

Here are two utility commands/scripts I use that help with this kind of thing. 1) get_plugins -- Show all plugins with their their docstrings. 2) Create Outline From Clipboard -- With a copied node or entire outline in the clipboard, create a new outline from it. Run *get_plugins * with

Re: How did I came across Leo?

On Wednesday, March 23, 2022 at 8:01:58 PM UTC gates...@gmail.com wrote: > On Wed, Mar 23, 2022 at 3:29 PM jkn wrote: > >> >>> >> Bl**dy hell, I remember now, there used to be forward and back arrows on >> the toolbar, didn't there? Why do I no longer see them?? >> >> > I think they're part

Re: How did I came across Leo?

On Wed, Mar 23, 2022 at 3:29 PM jkn wrote: > >> > Bl**dy hell, I remember now, there used to be forward and back arrows on > the toolbar, didn't there? Why do I no longer see them?? > > I think they're part of the nav_qt.py (or similarly named) plugin. Might not have it in @enabled-plugins :)

Re: How did I came across Leo?

On Wednesday, March 23, 2022 at 3:03:55 PM UTC tbp1...@gmail.com wrote: > On the subject of CTRL-clicking, Leo has a feature that is fantastic when > you are cruising around in its source code trying to learn how something > works. If you CTRL-click on a method invocation, you will get

Re: How did I came across Leo?

On Wednesday, March 23, 2022 at 2:41:05 PM UTC tbp1...@gmail.com wrote: > On Wednesday, March 23, 2022 at 10:21:50 AM UTC-4 jkn wrote: > >> A couple of points from this interesting list: >> >> > - the minibuffer is inherited from emacs, and serves ... a yet to >> discover number of functions

Re: How did I came across Leo?

On Wednesday, March 23, 2022 at 4:13:18 PM UTC+1 gates...@gmail.com wrote: > Being a programmer, the whole 'everything is scriptable, data is > accessible anywhere' bit really made me excited. > I'm not even sure I'm a programmer, but reading this, I guess I'm not. > Leo is pretty central

Re: How did I came across Leo?

I don't think anyone is going to do much more documentation - and it would be hard to organize in a way that is both helpful and practical to search. > if you want to do some Sphinx-style documentation > Actually, I discovered the existence of Sphinx as a side effect of my discovery of leo.

Re: How did I came across Leo?

On Wednesday, March 23, 2022 at 11:13:18 AM UTC-4 gates...@gmail.com wrote: > It's my primary IDE these days, and I've written quite a few 'LApps' > (leo-apps) that live inside their own outlines for various tasks -- > effectively custom tools. Leo is pretty central to how I interact with >

Re: How did I came across Leo?

On Wed, Mar 23, 2022 at 11:04 AM tbp1...@gmail.com wrote: > On the subject of CTRL-clicking, Leo has a feature that is fantastic when > you are cruising around in its source code trying to learn how something > works. If you CTRL-click on a method invocation, you will get transported > to its

Re: How did I came across Leo?

On the subject of CTRL-clicking, Leo has a feature that is fantastic when you are cruising around in its source code trying to learn how something works. If you CTRL-click on a method invocation, you will get transported to its definition. It misses once in a while, but usually works.

Re: How did I came across Leo?

Oh, yes, and when you get a long listing in a tab like the commands listing, you can select all the output with the usual CTRL-A and copy it with the usual CTRL-C. Then you can paste it somewhere that is more readable, like a Leo node or a text editor. On Wednesday, March 23, 2022 at 10:41:05

Re: How did I came across Leo?

On Wednesday, March 23, 2022 at 10:21:50 AM UTC-4 jkn wrote: > A couple of points from this interesting list: > > > - the minibuffer is inherited from emacs, and serves ... a yet to > discover number of functions > Personally I think 'minibuffer' is an unhelpful name, it's just an > interface

Re: How did I came across Leo?

A couple of points from this interesting list: > - leo ... includes ... a copy of an editor (CKEditor4) that is apparently written in Javascript Really?!? > - highlighted text (including URLs are NOT links. you need to copy/paste them to open (or maybe use a still-to-discover setting)

Re: How did I came across Leo?

It's true that there can be a huge learning curve if you want to get beyond the obvious and do some custom things. Yet if you learn to use @file and @clean files, and especially if you want to develop in Python, or do some Sphinx-style documentation, you can get that going pretty easily.

Re: How did I came across Leo?

Well, I came across leo last week, looking for a python IDE that would (potentially) - run on Windows - allow to make the resulting python run on a separate computer (same network but different subnet) for security reasons, maybe on Linux. - ideally, the python script could run with another

Re: How did I came across Leo?

On Sun, Mar 4, 2018 at 9:18 PM, Matt Wilkie wrote: >> ​ ​ @root and Leo's tangle and untangle commands will remain "forever". ​>>​ They are, on purpose, no longer documented, [...] > ​ ​ I would hope they are documented somewhere though? Perhaps within the code if no place

Re: How did I came across Leo?

> > ​@root and Leo's tangle and untangle commands will remain "forever". They > are, on purpose, no longer documented, [...] > I would hope they are documented *somewhere* though? Perhaps within the code if no place else. I imagine a future self shooting myself in the foot while I spin this

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: 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: 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: How did I came across Leo?

On Fri, Feb 23, 2018 at 11:35 AM, Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: > I came about Leo because I was interested in Learning Python and some > forum said that Leo, not Zope, was a superb showcase for this language and > then I found that it supported a form of literate

Re: How did I came across Leo?

I employed Leo for an oddball use case, which it addressed beautifully. How long ago did this start, perhaps 2005? The job that I held then required that, without help from work infrastructure or from colleagues, I write tools for diagnosing and repairing problems with installations of a

Re: How did I came across Leo?

On Tue, Feb 27, 2018 at 3:10 PM, Matt Wilkie wrote: Much as I love text I'm still a strong graphic creature. My dream writing > platform is all of the best parts of rich text & media editing fused with > Leo's node management and scripting. Bonus points if it's webby lets me >

Re: How did I came across Leo?

> > It has been almost 14 months since I discovered Leo and today I recalled > how I found it. > Thanks for this thread. I've been trying to recall my own path of discovery. No concrete memory has emerged, but it was somewhere in the intersection of being dissatisfied with wiki notes and

Re: How did I came across Leo?

On Fri, Feb 23, 2018 at 11:35 AM, Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: ​> ​ So, my path was Python -> Zope -> Leo -> Outlining for Literate Programming -> Writing -> Pharo, Roassal -> Reproducible research and data storytelling and visualization -> Grafoscopio. ​It's been

Re: How did I came across Leo?

Hi, I came about Leo because I was interested in Learning Python and some forum said that Leo, not Zope, was a superb showcase for this language and then I found that it supported a form of literate programming, which I was already interesting into. I started to use it almost exclusively for

Re: How did I came across Leo?

I think I discovered Leo as a result of a fleeting interest in literate programming. Don't recall the date, but it was before Leo was ported from C++ to Python. When I learned that Edward lived across town, kitty-corner from a high school sweetheart, I was SOLD! :-] On Thu, Feb 22, 2018 at 8:39

Re: How did I came across Leo?

On Thu, Feb 22, 2018 at 10:27 PM, Terry Brown wrote: > > I think I was using Freemind before Leo, although I'd spent a long time WoW .. in fact, there really some guys base Leo record notes, and translate into Freemind xml for export maindmapping html. > using the console

Re: How did I came across Leo?

I think I was using Freemind before Leo, although I'd spent a long time using the console based outliner hnb, which apparently has been resurrected as tines https://github.com/larrykollar/tines Cheers -Terry -- You received this message because you are subscribed to the Google Groups

Re: How did I came across Leo?

I found Leo when I was looking for an outliner that supported clones, ran on Linux, and wasn't a website. I live on a farmlet on the edge of the world and our internet has always sucked. I took Leo up in 2007. And if there is one thing I have learned in the interval it is that with Leo, anything

Re: How did I came across Leo?

I found Leo when I was looking for a replacement for ECCO (anyone remember that program?) I used ECCO for 15 years after it wasn't supported anymore and the core group of diehard users finally lost hope the program owners would open source the code. Anyway, I don't remember how long ago that