Re: Please send screenshots!

Among the other things, I am using Leo increasingly often to manage complex config files. I find Leo especially useful when managing my Emacs configuration. I have a number of Emacs config files structured as Leo outlines, each file corresponding to a @clean branch. One of these files is

Re: Please send screenshots!

This idea could be revived for 5.5 now that documentation is going to be more direct and screenshots of current or previous uses of Leo by different users in the community could help on that. Here is my contribution showing how Leo can help you to structure/draft/write long complex documents

Re: Turning to documentation

And maybe from docs as mini programs to live docs as live mini-programs ;-)... interesting times are coming from Leo and literate computing and maybe another important breakthrough in the 20+ Leo's history. Cheers, Offray On 09/02/17 11:55, Edward K. Ream wrote: ​​ On Thu, Feb 9, 2017 at

Re: Mini-tutorial: using clones safely. Pls read

Clones were one of my most attracting features and one place where Leo is offering unique features on data emergent order. This documentation is direct and clear. May be some screenshots could improve the attractiveness of clones. Cheers, Offray On 22/02/17 12:06, Edward K. Ream wrote: I

Re: Proposed actions re: #350: themes not working as documented

May be some minibuffer command to preview and apply themes should be a newbie friendly solution (or a notebook that does that via nodes). Cheers, Offray On 03/03/17 10:20, john lunzer wrote: From a newbie's perspective I like the idea of themes being centrally located in their own .leo file

Re: Well Kent, your vision for Leo is becoming clearer

Hi, On 07/03/17 11:56, john lunzer wrote: [...] I'd love to hear more about this or read some docs about what you're working on. Any time I hear the word 'spatial' in relation to data my ears perk up a little. Maybe you will enjoy this video that shows software architecture as data and

Re: Leo and abstraction

Thanks for your testimony John. I have given some similar testimony [1]. I'm trying to bring some Leo ideas to the Pharo live coding environment by prototyping them and some other back here by discussing on the list. [1] http://leoeditor.com/testimonials.html#offray-luna-cardenas The idea of

Re: Downloading Leo - suggestions

Hi, I like how documentation is getting more compact and direct. I wonder if installation instructions could go from the most newbie friendly to the not so newbie ones (maybe after releasing 5.5). So installation should start from the most common used installation method of the intended

Re: plans to add markdown support and/or syntax highlighting

On 20/03/17 17:23, Edward K. Ream wrote: On Mon, Mar 20, 2017 at 12:23 PM, marquis patrick > wrote: leo is pretty awesome, it would be even more so if it could support markdown rendering and syntax highlighting support as well.

Re: plans to add markdown support and/or syntax highlighting

On Mon, Mar 20, 2017 at 12:23 PM, marquis patrick wrote: leo is pretty awesome, it would be even more so if it could support > markdown rendering and syntax highlighting support as well. > I think if combined with the features from Quiver https://github.com/ >

Re: Wanted: someone to create mac brew install

On Mon, Mar 20, 2017 at 4:48 PM, marquis patrick wrote: > What kind of timelines are you looking at? I'm an adept mac user but not > have never created mac brew package. Would be willing to be give it a go > ​Excellent. Thanks very much. You can't really begin until

Re: Wanted: someone to create mac brew install

What kind of timelines are you looking at? I'm an adept mac user but not have never created mac brew package. Would be willing to be give it a go On Monday, March 20, 2017 at 6:29:59 AM UTC-5, Edward K. Ream wrote: > > This is an important issue. It can only be done after a final release,

Re: A sprint (real or virtual) about Leo 5.6

On Monday, March 20, 2017 at 9:03:33 AM UTC-5, Edward K. Ream wrote: Leo probably should allow arguments to @language, as in org mode > . > > If we actually do this, we are likely going to

Re: All Leo issues could be called virtual sprints

On Monday, March 20, 2017 at 9:08:17 AM UTC-5, Edward K. Ream wrote: > > The discussion of 5.6 features > is > getting unwieldy. Instead of a monolithic discussion, I'll be creating > separate enhancement items. In fact,

Re: A sprint (real or virtual) about Leo 5.6

On Monday, March 20, 2017 at 9:03:33 AM UTC-5, Edward K. Ream wrote: Leo should support the following extension of the execute-script command. > If there is no text selection, execute-script should use only the code from > the present insert point back to the previous @language directive (in

Re: A sprint (real or virtual) about Leo 5.6

On Monday, March 20, 2017 at 8:44:01 AM UTC-5, Edward K. Ream wrote: - Add p.drawer and related items >> >> >> > > A pop-up edit widget showing p.drawer will

All Leo issues could be called virtual sprints

The discussion of 5.6 features is getting unwieldy. Instead of a monolithic discussion, I'll be creating separate enhancement items. In fact, several already exist. I'll be creating new items next, with links to them in

Re: A sprint (real or virtual) about Leo 5.6

On Monday, March 20, 2017 at 8:44:01 AM UTC-5, Edward K. Ream wrote: *New item*: Support p.results. Again, p.results will be a Python property, > using uA's behind the scenes. Unlike p.drawer, results will not > necessarily be strings. Any picklable values should be allowed, and > possibly

Re: A sprint (real or virtual) about Leo 5.6

On Monday, February 27, 2017 at 8:11:08 AM UTC-6, Edward K. Ream wrote: Several new features do stand out: > > - Better integration with .org files, say by supporting .leo.org or > org.leo files. > Still important. > - Replace attrib_edit by p.drawer. >

Wanted: someone to create mac brew install

This is an important issue. It can only be done after a final release, and only by somebody who is more adept with MacOS than I. Any help would be greatly appreciated. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from