Re: HTML 5 Leo Viewer

There is certainly a lot to think about here. As Edward stated, keeping up with the Javascript world is a daunting task if you've already deeply immersed in a whole other world. To address your OP, there is currently a long term goal of investigating using Flexx to build a web-based GUI for

Re: solution: clearDirty @ nodes when working with chapters/organizational nodes

After using these for a few days I think mark-node-clean and mark-subtree-clean commands would be nice additions to the core. On Friday, March 3, 2017 at 1:27:00 PM UTC-5, john lunzer wrote: > > A design decision was made in Leo that if you alter the heading/body of > any parent of

solution: clearDirty @ nodes when working with chapters/organizational nodes

A design decision was made in Leo that if you alter the heading/body of any parent of an @ node that this node will be marked dirty, ie it will be written to disk when saving the .leo file. After discussion I agree it's the safest option. However, when using chapters and organizational nodes

Re: Leo and abstraction

are > also helpful (backlinks, unls, bookmarks, tags, even clones ;-) > > Cheers -Terry > > ------ > *From:* john lunzer <lun...@gmail.com > > *To:* leo-editor <leo-e...@googlegroups.com > > *Sent:* Friday, March 3, 2017 9:11

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

>From a newbie's perspective I like the idea of themes being centrally located in their own .leo file and having a button from that separate file to copy a specific theme to myLeoSettings.leo without having to open or fiddle around in myLeoSettings.leo. I think that level of separation will

Leo and abstraction

Warning: This is a testimonial, sorry. Lately I've been thinking about programming in general. My thoughts have centered on the limits of the human brain to understand computer programs. This was triggered by watching Inventing on Principle . It's a

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

t.com/dataweek/ > > If I would have to choose only one feature to be enabled in Leo 5.6 that > would be literate computing (even if is limited "only" to Python). > > Cheers, > > Offray > > On 01/03/17 09:48, john lunzer wrote: > > While it would b

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

While it would be pretty great to have full auto-reformatting ascii org-mode tables my inclination is that there are higher priority org-mode features that should be tackled first (for example, functionality enabling literate programming). On Wednesday, March 1, 2017 at 8:39:25 AM UTC-5, Arjan

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

On Monday, February 27, 2017 at 9:11:08 AM UTC-5, Edward K. Ream wrote: > > - Support for pyzo's client/server based shell. It this needed? Do > valuespace or python_console plugins suffice? I suspect pyzo's architecture > is better, but I'm not sure how much better. > > Edward > If we're

Re: New: reload-settings and reload-all-settings (including abbreviations!)

Been meaning to post this, but I also am receiving a similar error. -- 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

Re: PgUp/PgDown ! tree key shortcuts

hink a lot of people break the quotes convention. Some people just prefer one or the other. On Thursday, February 23, 2017 at 7:46:36 AM UTC-5, jkn wrote: > > > > On Tuesday, February 21, 2017 at 9:24:20 PM UTC, john lunzer wrote: >> >> I usually use the quicksearc

Re: Python 2.7 custom commands in c.commandsDict as unicode

Okay thanks for responding, just checking. On Wednesday, February 22, 2017 at 11:50:39 AM UTC-5, Edward K. Ream wrote: > > > > On Wed, Feb 22, 2017 at 10:09 AM, john lunzer <lun...@gmail.com > > wrote: > >> I was just poking around and I was looking at a co

Python 2.7 custom commands in c.commandsDict as unicode

I was just poking around and I was looking at a couple of my custom commands and the keys are registered in the command dict as u'' (ie unicode) while Leo's native commands are not unicode. My guess is that this could cause issues and the keys for custom commands should be store the same as

Re: PgUp/PgDown ! tree key shortcuts

On Tuesday, February 21, 2017 at 8:52:29 PM UTC-5, Edward K. Ream wrote: > > ​ > This would be a big project. I don't think it is worth doing now. I have > in mind a few baby steps, but even these don't seem all that important > compared to other possible projects. > > Agreed. I think once

Re: PgUp/PgDown ! tree key shortcuts

expected it's probably lower priority. On Tuesday, February 21, 2017 at 3:29:30 PM UTC-5, jkn wrote: > > > > On Tuesday, February 21, 2017 at 6:49:15 PM UTC, john lunzer wrote: >> >> I've set these key shortcuts: >> >> goto-next-n-visible ! tree = Page

PgUp/PgDown ! tree key shortcuts

I've set these key shortcuts: goto-next-n-visible ! tree = PageDn goto-prev-n-visible ! tree = PageUp Here is my @command goto-next-n-visible node: @language python N=12 def getVisNextN(n): current = c.p for ind in range(n): forward = current.getVisNext(c) if

Re: can't get parse-body to do anything...

to be better documented. As the result of "help for command" for "parse-body" is essentially empty. On Tuesday, February 21, 2017 at 8:39:10 AM UTC-5, jkn wrote: > > Hi John > > On Tuesday, February 21, 2017 at 1:01:26 PM UTC, john lunzer wrote: >> >> I tried

Re: can't get parse-body to do anything...

I tried this code too. Once without @language python, in which it failed, and once with @language python, in which it was successful. So please make sure that this directive is included in a parent of the branch you're trying to parse-body on. On Tuesday, February 21, 2017 at 6:05:12 AM UTC-5,

Re: Marketing, features and newbies

I think every time we have one of these impromptu "let's make Leo great again" brainstorming sessions I think the core users (which are represented on these forums) are end up being really hard on Leo (and by proxy you Edward). I've been through a couple of these so my take is that the

Re: What are your favorite abbreviations?

hl;;={|{x=c.p.h}|} es;;=g.es(contents,color='<|color|>') ts;;={|{x=time.strftime("%Y%m%d%H%M%S")}|} Without doubt hl;; is my most used. Unfortunately two of those also use scripting abbreviations, but honestly if you're not using scripting abbreviations you're not getting the full abbreviation

Re: Leo 5.5 will challenge org mode

deletions off screen. > > [image: Inline image] > Cheers -Terry > > > -- > *From:* john lunzer <lun...@gmail.com > > *To:* leo-editor <leo-e...@googlegroups.com > > *Sent:* Friday, February 17, 2017 1:56 PM > *Subject:* Re: Leo 5.5 will challenge org

Re: Leo 5.5 will challenge org mode

On Friday, February 17, 2017 at 3:46:54 PM UTC-5, Terry Brown wrote: > > vs-eval / vs-last / vs-pretty do this. I added them to the inscrutable > valuespace plugin because it already creates a common namespace (c.vs), but > really they should be separate, seeing they're straight forward and

Re: Leo 5.5 will challenge org mode

Really glad to see the idea of multiple body panes is gaining traction. Along with optionally being able to show the node headlines, as you suggested, there should also be an option to indent the entire panes to match the tree indentation. Org-mode has this toggle. On Friday, February 17, 2017

Re: About org mode

1. Agree, auto-formatting tabular data in Org-mode is one of the central features. 2. I will go back to my "continuous edit pane" idea. I think if you really want to recreate Org-mode and make it attractive to those familiar with Org-mode there must be a "continuous edit pane" mode for Leo.

Re: commands to move to next file in 'file edit list'?

for "unix teletype keyboards" reveals that for some there was neither PgUp/PgDown or Prior/Next. On Thursday, February 16, 2017 at 11:10:15 AM UTC-5, jkn wrote: > > Hi John > > On Thursday, February 16, 2017 at 3:19:00 PM UTC, john lunzer wrote: >> >> Also loo

Re: commands to move to next file in 'file edit list'?

Also looks like Ctrl+Tab performs the same function as Ctrl+PgDown On Thursday, February 16, 2017 at 7:21:17 AM UTC-5, john lunzer wrote: > > I believe these are already bound to Ctrl + PgUp/PgDown. If not let me > know and I'll fish them out. > > On Thursday, February 16, 2017 at

Re: commands to move to next file in 'file edit list'?

I believe these are already bound to Ctrl + PgUp/PgDown. If not let me know and I'll fish them out. On Thursday, February 16, 2017 at 6:43:13 AM UTC-5, jkn wrote: > > Hi all > possibly-dumb question, although I can't find it in the cheat sheet > for via print-commands: > > If I have

Re: Leo's HOME directory

aps a custom cd() function that does both get_last_cwd() and > save_last_cwd() at once, saves having to remember to use the other > functions. > > Cheers -Terry > > > -- > *From:* john lunzer <lun...@gmail.com > > *To:* leo-editor <leo-e...@go

Re: Please review Leo's new 10-minute intro

I think a new Leo main screenshot is in order. When I new user opens Leo for the first time, says to themselves, "I have no idea where to go from here. I had better read the docs", and then actually goes to the docs they should be reassured that the docs are relevant to what they're seeing in

Re: Leo's HOME directory

I'll use this thread because it seems relevant. I'm trying to do some experiments using Leo as a shell. Amongst other things I'm trying to change this current working directory. I have a small node script: @language python import os os.chdir("..") g.es(os.getcwd(), color="green") Perhaps

Re: Leo in 5 minutes

I think what you said about the "over the shoulder" concept of learning is potentially the most powerful way to bring people up to speed. Some people will still prefer traditional "read the docs" style documentation but many will prefer narrated "demo.py" style demos showing them *exactly* what

Next-gen edit pane enabling org-mode and jupyter like experiences, and much more

Terry, since you are working on Leo's next generation edit pane anyway I thought I'd at least throw the idea out there to see if it resonated with where we'd like to take Leo's body pane. Edward, I'd like to get your take as well as it could impact many goals coming up. I call it "continuous

Inventing on principle

I was guided to this presentation another presentation by a former prominent Scala developer (Paul Phillips). The presentation by Bret Victor is called, *Inventing on Principle*: https://www.youtube.com/watch?v=PUv66718DII I will only preface the video with Paul's quote: > If you don't come

Re: Warning: imp.reload hurts super and TDD

Edward, doesn't that statement just scream "*something is wrong with this*" to you? Your time is the most precious resource you have. My advice is to do a freeze of Leo (and it's documentation) at version 5.5 or 5.6 as the last Python 2 compatible version. Make this version available

Re: ENB: urls and pictures in the body pane

Offray's Grafoscopio has some kind of mind map type view mode which he has used for presentations which displays images with texts. Initially just the headers are visible but he can expand the "node" and the body will show text /images. Anyway it's not the same as what you're doing here but it

Re: Leo 5.5b1 coming soon

sm rather than born from feelings of jealousy or inadequacy. We are almost always our own worst enemy (unless one has an arch nemesis) and so it's easy to see one's own strengths in a diminished light. On Friday, January 27, 2017 at 11:22:37 AM UTC-5, Edward K. Ream wrote: > > ​​ > On F

Re: Leo 5.5b1 coming soon

An improved scripting tutorial would be great, but the demo-it tool in python would be awesome. Great stuff Edward. Thank you for all of your work. It's fun to watch you when you're excited about Leo. I've been around long enough to see your "down" periods. I don't know what goes on in those

Re: Leo and fossil

7 at 11:30:00 AM UTC-5, Offray Vladimir Luna Cárdenas wrote: > > > On 25/01/17 19:56, john lunzer wrote: > > Nice, pretty much what I imagined it would look like. Now that I think > about it statistical analysis of nodes can be done completely separately > from node history.

Re: Leo and fossil

Nice, pretty much what I imagined it would look like. Now that I think about it statistical analysis of nodes can be done completely separately from node history. Just need to track each edit with a timestamp. -- You received this message because you are subscribed to the Google Groups

Re: Leo and fossil

ially hiding right under your feet. A truth that could have the power to transform the way you work. That said, I'm truly not trying to affect your focus, I think your current priorities are good. On Tuesday, January 24, 2017 at 3:36:10 AM UTC-5, Edward K. Ream wrote: > > ​​ > ​On Mon, Jan 2

Re: New Leo edit control

; wrote: > > > On Mon, Jan 23, 2017 at 11:42 AM, john lunzer <lun...@gmail.com > > > > wrote: > > > > > Of the code editor's I've used code comparison is encouraged within > > > a single running application, this allows for fancier things li

Re: Leo and fossil

Well, if I'm being honest this is all theoretical in my mind. I've been looking into Fossil more and just the name triggers ideas. Fossil was chosen as a name due to the fact that all artifacts in Fossil are immutable and could be thought of as fossils. The imagery of archaeology is what I

Re: Leo and fossil

Been mostly on the sidelines on this one, mostly because I didn't have time to think about it. I think node versioning is a potentially "killer app". Having a fully automatic document versioning system at the .leo file level and node level would be a turbo boost in project organization and

Re: Tip: use separate windows to compare code

If thinking forwards. I would not consider the idea "dead". If in the future there are multiple front-ends (Qt/HTML-Javascript/curses) then it might make sense to do this in body editors rather than opening up a whole new Leo. In saying that I'm not trying to induce action, just consideration

Re: Two outliners with live coding support

I only watched the first demo. As you alluded to, I was struck by how similar that workflow looked to Jupyter. It is certainly awesome. Edward, I'm glad you are gaining inspiration from it. Offray, thank you for sharing! Outliners (mainly Leo) have become essential to my productivity and I

Re: ENB: pyzo syntax coloring: progress and a big mystery

If you think you've hit a wall. I would not hesitate to contact Almar, he has been extremely responsive to my questions in the past. On Thursday, January 12, 2017 at 11:39:26 AM UTC-5, Edward K. Ream wrote: > > On Thu, Jan 12, 2017 at 10:13 AM, 'Terry Brown' via leo-editor < >

Re: Improving Leo using pyzo code

Flexx yesterday and it is brilliant! > > On Wednesday, January 11, 2017 at 7:43:44 PM UTC+8, Edward K. Ream wrote: >> >> >> >> On Sun, Jan 8, 2017 at 3:17 PM, john lunzer <lun...@gmail.com> wrote: >> >>> So awesome that you made this discovery, I've wanted

Re: Improving Leo using pyzo code

Just had to post again after reading the other recent post with Offray. Everything you talked about integration into Leo will be amazing. Full IPython/Jupyter integration will super charge Leo. If all of Leo's internals are exposed via a fully integrated IPython kernel the interactivity of Leo

Re: Improving Leo using pyzo code

So awesome that you made this discovery, I've wanted to try Pyzo out for some time now. You may be aware that the author of Pyzo is also the author of Flexx. It's great to see great artists getting inspiration from other great artists. Can't wait to see what comes of these developments. The

Re: leo stalling for long periods

Yes, this was me because I almost exclusively access files over a slow vpn on network drives. Here is the issue in question . I actually never tested this change. I'll try to turn it on at some point soon. On the other hand, the date Curtis

Re: Bad bugs *are* possible in python & Leo

I've heard the claim that interpreted languages simply have a whole different set of bugs than compiled languages. I think about 95% of the bugs I encounter in Python at runtime are due to incompatible types due to an "inappropriate" type/value being passed to a function. Sometimes it's

Re: Theme Problems

It's possible the tests need to be updated. Rather than run the tests, have you recently done a fresh checkout of Leo and followed the theme instructions? I believe that is what both Terry and I did and how we concluded that themes are non-operational. On Thursday, December 15, 2016 at 6:20:19

Re: leo stalling for long periods

I have also had to make this change because most of my files are on network locations. On Wednesday, December 14, 2016 at 5:59:17 PM UTC-5, Terry Brown wrote: > > Looking around a bit more, looks like you can disable those file checks > with > > @bool check_for_changed_external_files = False >

Re: Theme Problems

I'm testing on the current master as of today and themes are not working as advertised on Linux/Python3/PyQt4. I can copy my old "theme" node headlined "leo_dark theme 0" from my daily driver version of Leo to my test master and it will load fine. The important node to this "theme" is

Re: Option to determine which @ directive to use when opening non-.leo files from the command line

I moved forward on this myself, at least the command line option part. Please see pull request here: https://github.com/leo-editor/leo-editor/pull/349. On Tuesday, December 13, 2016 at 11:01:38 AM UTC-5, john lunzer wrote: > > In my explorations of Leo in trying to make Leo usefu

Option to determine which @ directive to use when opening non-.leo files from the command line

In my explorations of Leo in trying to make Leo useful from the command line I'm faced with the limitation that it seems that when opening a non-.leo outline file from the command it's hard coded to open these files as @edit nodes. I am suggesting/requesting that an option be added to Leo to

Re: Why I don't use Leo more often

ly Windows users won't care about a GUI plugin so I'm not so concerned about that. In any case, I'd like to *try* to make some moves on this but I expect it will be slow going at best. On Sunday, December 11, 2016 at 4:16:30 AM UTC-5, Edward K. Ream wrote: > > > > On Fri, Dec 9, 2016 a

Re: Why I don't use Leo more often

Sorry for commentary on previous post. You said you had fixed enough crashers, I'm wondering if some methods changed since you made your original fixes which broke the curses GUI. On Thursday, December 8, 2016 at 2:40:53 PM UTC-5, john lunzer wrote: > > I'm getting a traceback when I try

Re: Why I don't use Leo more often

eo-editor/leo/core/leoCommands.py", line 6730, in setHeadString c.frame.tree.setHeadline(p, s) AttributeError: 'textTree' object has no attribute 'setHeadline' On Friday, November 18, 2016 at 8:57:56 PM UTC-5, Edward K. Ream wrote: > > On Fri, Nov 18, 2016 at 11:13 AM, john lunzer <

Re: --diff: Leo as an external git diff

As you've stated, Leo seems uniquely suited towards tasks of this nature. I could even imagine full git integration, I imagine never having to leave the confines of Leo to work on a project and manage it in Git. On Wednesday, December 7, 2016 at 11:33:03 AM UTC-5, Edward K. Ream wrote: > > On

Re: Wanted: students for the Leo Code Academy

Thank you for the quick overview of your methods. On Saturday, December 3, 2016 at 5:50:20 PM UTC-5, Edward K. Ream wrote: > > On Sat, Dec 3, 2016 at 3:58 PM, john lunzer <lun...@gmail.com > > wrote: > >> >> Like djc, I found Leo's source a little overwhelming but a

Re: Wanted: students for the Leo Code Academy

If I may piggyback on djc's statement. I am in a similar situation. I work full time and have children so my time is short. I reached out to Ville about six months ago to ask him why he became inactive with Leo and he said "I have a family now, I didn't when I was active". It is sad that there

Re: All importers have been converted!

> > After that, my hands are telling me I need a break. We'll see whether I > listen to them. I really should... > Considering you said the same a week ago and didn't, this time you really *should* give them a break. Thank you for your work, it is delightful to see you active and excited.

Re: where re-define default color? [was] how to setup Leo cursor size and highlight currently line?

, Zoom.Quiet wrote: > > as atta. snap. > base john lunzer <lun...@gmail.com > suggest config: > ~/.leo/myLeoSettings.leo#@settings-->Syntax > coloring-->Language-specific colors-->Python > > reply-to: leo-e...@googlegroups.com > to: leo-editor <leo-e...@goo

Re: Why I don't use Leo more often

make working as remote ;-) > > > > On Fri, Nov 18, 2016 at 11:13 AM, john lunzer <lun...@gmail.com > > wrote: > > I use Leo as my primary editor when I can. > > > > When I can't is when I'm SSHing into machines remotely where it is often > not > >

Re: 97587a8: The new python importer is now active

Swapping Left-Ctrl with Capslock is probably the single greatest change one can make to reduce overall finger travel distance. On Friday, November 18, 2016 at 1:06:02 PM UTC-5, Edward K. Ream wrote: > > On Fri, Nov 18, 2016 at 10:46 AM, john lunzer <lun...@gmail.com > > wrote:

Why I don't use Leo more often

I use Leo as my primary editor when I *can*. When I can't is when I'm SSHing into machines remotely where it is often not practical (or desirable) to run GUI applications. I believe there was some work done on a curses front-end plugin in the past but I'm not sure how far that got. I would

Re: 97587a8: The new python importer is now active

> > I am being mindful about what causes additional pain. > Out of curiosity, what do you believe is responsible for causing your pain? I have a great interest in RSI related issues when it comes to interacting with computers. I use a homerow keyboard setup using autohotkey so that I very

Re: Note to devs: why I commit so often

Sounds like a best practice to me ;) On Friday, November 18, 2016 at 10:31:54 AM UTC-5, Edward K. Ream wrote: > > It's simple: each commit marks a place at which all unit tests pass. So > each commit is a rollback point in case things go wrong. Given the > complexity of the present cleanup

Re: Python Anywhere

hought. On Monday, November 14, 2016 at 3:03:45 PM UTC-5, john lunzer wrote: > > Others have stated great reasoning. So I don't want to recap but I'll add. > > In the cloud age "traditional platform" doesn't mean what it used to. The > Leo "server" needn't be

Re: Python Anywhere

Others have stated great reasoning. So I don't want to recap but I'll add. In the cloud age "traditional platform" doesn't mean what it used to. The Leo "server" needn't be your computer, but could be a cloud based virtual machine that with guaranteed accessibility and uptime. As a pure

Re: Python Anywhere

Lab demo looked pretty good. > > Cheers -Terry > > -- > *From:* Edward K. Ream <edre...@gmail.com > > *To:* leo-editor <leo-e...@googlegroups.com > > *Sent:* Monday, November 14, 2016 1:30 PM > *Subject:* Re: Python Anywhere > > > > O

Re: Python Anywhere

> > https://github.com/jupyterlab/jupyterlab > > Cheers, > > Offray > > On 14/11/16 11:22, Edward K. Ream wrote: > > On Mon, Nov 14, 2016 at 10:10 AM, john lunzer <lun...@gmail.com > > wrote: > >> Web-based front-end simply means that the GUI runs

Re: Python Anywhere

Web-based front-end simply means that the GUI runs in a browser. My understanding of Flexx is that you can use it in the same way that you would use PyQt. I do not believe it places restrictions on the rest of your Python code. I do agree that the language on the docs site is a bit obtuse. If

Re: Leo proposed logo and icon design

read my last response in this thread? The logo is not unique, (as > the current one) and can be obtained from svg downloading sites. If we're > going to change the current logo, we could search for one that identifies > the community and Leo in a non-generic way. > > Cheers, > > Offr

Re: Leo proposed logo and icon design

Amine, the proposed logo is beautiful. It's crisp and geometrically striking, this is a "strong" and "proud" lion. This represents most of what you would want in a logo. I will counter Edward's argument. First, Leo does not really have a "brand" at this point, it has a small following. Leo's

Re: Python Anywhere

I think it is more likely that a browser-based *front-end *can be achieved, rather than trying to host Leo itself in the browser. In this way you could host *your* Leo from your home/work computer or a cloud instance. The thought of this is pretty exciting to me. I believe that Flexx

Re: Why is Leo great?

Thank you for putting in the time and effort to learn Leo. My story with Leo mirrors Matt Wilkie's to some extent. I have contributor access to Leo's GitHub, I think mostly because of the level of complaining I did and Edward just wanted to shut me up (just kidding). I have been a strong

Re: Leo reimagined: a tree/dag/view for every attribute!!!

That is pretty rad, thanks for sharing! On Wednesday, June 1, 2016 at 7:26:37 AM UTC-4, Conor White-Sullivan wrote: > > This is amazing to come across. > > I discovered Leo today after scouring the web trying to find some UI where > people were merging trees to create this a multi-dimensional

Re: Leo and Eve

AM UTC-4, Edward K. Ream wrote: > > On Mon, May 16, 2016 at 10:49 AM, john lunzer <lun...@gmail.com > > wrote: > >> It is a true shame that pudb is non-windows only. >> > ​ > Perhaps there is a workaround. > ​ > >> I wasn't exactly impl

Re: Leo and Eve

ally gives a tangible feel to code. On Monday, May 16, 2016 at 11:24:22 AM UTC-4, Edward K. Ream wrote: > > On Monday, May 16, 2016 at 10:01:49 AM UTC-5, Edward K. Ream wrote: >> >> On Mon, May 16, 2016 at 8:02 AM, john lunzer <lun...@gmail.com >> > wrote: >> >&

Re: Leo and Eve

I realize this was not aimed at me, but this direction you speak of *is* exciting. I already use Leo + IPython to perform some form of "live coding", even manipulating Leo which is helpful in understanding Leo. But I mainly perform all of that interaction from the IPython console. It appears

Re: Leo and Eve

For Eve this diary of a former developer is perhaps the most telling. Only the very beginning is relevant to Eve, here is an interesting snippet: However, it's [Eve] not yet useful for *me*. I spend my days building > compilers and IDEs,

Re: Leo and Eve

Sorry for the delayed response here, the "summary" of Leo was from me. I believe Joshua was the one who started the thread. On Thursday, May 12, 2016 at 2:24:46 PM UTC-4, Edward K. Ream wrote: > > > > On Fri, May 6, 2016 at 3:44 PM, Joshua Olson <0joshua...@gmail.com > > wrote: > >> That was

Re: Leo and Eve

Oh boy! Posted over there if anyone is interested in my diatribe. On Friday, May 6, 2016 at 1:21:38 PM UTC-4, Kent Tenney wrote: > > (gotta be a Genesis joke in there somewhere ...) > > FYI > > I'm not sure how best to link to posts to other lists, so I've copied and > pasted > > So, Leo

Re: Leo and Eve

Oh boy! On Friday, May 6, 2016 at 1:21:38 PM UTC-4, Kent Tenney wrote: > > (gotta be a Genesis joke in there somewhere ...) > > FYI > > I'm not sure how best to link to posts to other lists, so I've copied and > pasted > > So, Leo appeared on the Eve mailing list. Eve is a project of Chris >

Re: Any way to kill/restart the IPython kernel?

rote: > > > > On Thu, May 5, 2016 at 10:00 AM, john lunzer <lun...@gmail.com > > wrote: > >> Yes, have tried closing the IPython window and use ipython-new, to no >> avail. The thing is IPython doesn't become unresponsive on it's own. I've >> only had is

Enhancement: Show global line number in lower left status bar

It just occured to me that I can "goto-global-line" but I can't see the global line number. If this wouldn't be too hard it would be quite useful information I think to show the global line number, there appears to be plenty of room. I was working with somebody who doesn't use Leo and they

Re: Any way to kill/restart the IPython kernel?

. On Thursday, May 5, 2016 at 10:26:37 AM UTC-4, Edward K. Ream wrote: > > > > On Thu, May 5, 2016 at 8:09 AM, john lunzer <lun...@gmail.com > > wrote: > >> Every once in a while my ILeo IPython kernel becomes unresponsive. The >> IPython window itself will look normal

Any way to kill/restart the IPython kernel?

Every once in a while my ILeo IPython kernel becomes unresponsive. The IPython window itself will look normal but when trying to execute anything from that window or through ipython-exec I get nothing in return. I haven't submitted this as a bug because I have no idea when this is happening to

Re: Proposal: remove emacs-style abbreviation commands

I didn't even know we could add abbreviations on the fly! -- 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

Re: @bool plain_key_outline_search = True

I too find it irritating and disorienting. Good addition. On Wednesday, May 4, 2016 at 4:04:53 PM UTC-4, Edward K. Ream wrote: > > A new setting, True by default so default behavior doesn't change. > > When False, it suppresses the headlines search feature, which I am finding > increasingly

Re: WormClones

I am using declutter-tree to great effect here. Class nodes are highlighted in pale pink and I am using an icon to replace "@worm". I am using a customized currently selected node style as well. The result is visually clean, interesting and appealing. On Wednesday, May 4, 2016 at 1:57:3

Re: can not load enabled plugin: viewrendered3 bigdash

Thank you for the investigative work. On Tuesday, May 3, 2016 at 10:17:28 AM UTC-4, Sami J wrote: > > Lewis, > I had the same issue and I noticed that QtWebKit and QtWebKitWidgets had > not been installed at all by the current Windows installers for PyQt5 5.6.0. > They are not even packaged in

Re: Proposal: remove emacs-style abbreviation commands

I use abbreviations but have never used an abbrev-* command. I am unsure of their function. On Tuesday, May 3, 2016 at 10:17:06 AM UTC-4, Edward K. Ream wrote: > > Does anyone use the static abbrev-* commands? I can see no use for them. > > The abbreviations in `@data

Re: Clarify theme instructions

This is a very important step! As without it you're not going to see any change. Good catch. On Friday, April 29, 2016 at 8:53:46 AM UTC-4, lewis wrote: > > May I suggest an update to clarify the instructions in > leoSettings.leo#@ignore Themes: copy to last top-level setting in >

Re: Leo 5.3-b1 released

Great work Edward. On Friday, April 29, 2016 at 6:38:40 AM UTC-4, Edward K. Ream wrote: > > Leo 5.3-b1 is now available on SourceForge > . Leo is a PIM, an IDE > and an outliner, but you knew that ;-) > > > Many thanks to

Re: Bug: expand-next-level keeps counting beyond maximum level

it. Subsequently using the up arrow will skip over the subtree again. I do not believe this to be the intended behavior. If you wish I can submit an issue detailing this thread. I presume no timetable, as I said this is a pretty low priority. On Thursday, April 28, 2016 at 11:49:36 AM UTC-4, john lunzer

Re: Bug: expand-next-level keeps counting beyond maximum level

No problem. This is a lower priority. On Thursday, April 28, 2016 at 11:35:25 AM UTC-4, Edward K. Ream wrote: > > On Thu, Apr 28, 2016 at 10:15 AM, john lunzer <lun...@gmail.com > > wrote: > >> You're right, it's not chapter related. But there is still a bug. >> >

Re: Bug: expand-next-level keeps counting beyond maximum level

6 at 6:59 AM, john lunzer <lun...@gmail.com > > wrote: > >> There is a small bug with expand-prev-level and chapters. You must have a >> chapter with a one child node at the next level and then any number of >> child nodes at the levels after that. >> &g

<    1   2   3   4   5   6   >