Does move-lines-up mess up syntax colouring?
Hi! I just discovered Leo, am amazed and already started hacking on it for the last 8 hours. The first thing I found out is that when I use move-lines-up on a python line to move it into a docstring, the syntax colouring does not end properly after the closing quotes of the docstring anymore (everything below gets green). Can anyone confirm this? Try transforming @language python def test(): a b c print 1 print 2 into @language python def test(): a b c print 1 print 2 by using move-lines-up on the print 1 line. -- You received this message because you are subscribed to the Google Groups leo-editor group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/VbQqOqSYRXwJ. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: Visions of Leo 5.0
We use leo quite a lot here at our company. I would say we are moderately technical users, but still have a lot to learn about leo! This is the key problem, however. We do a fair amount of Python coding in our business, but don't have time to constantly dig through the source code of every tool we use. It seems quite difficult to get up to speed on all of the capabilities of leo. Even by frequent, careful reading of the online help and a couple of years of everyday work with leo, we come away feeling like there is so much more there that we can't readily access. We monitor these forums and occasionally post questions and comments, but it feels like to really have an awareness of leo's feature set, you have to spend significant time reading the code and understanding it and continuously keep track of this forum. Much of capability discussions on this forum address really interesting items which don't seem to be addressed in documentation anywhere. This leaves the moderately technical to pure users wanting. It would be fantastic if all the great things about leo could be documented thoroughly so that potential new users could readily access these capabilities. It seems that the code and features within leo develop pretty rapidly, but much of it gets left undocumented. The only 'documentation' seems to be snippets of discussion threads on this forum. Much of the documentation is probably adequate for professional computer scientists, but leaves a significant gap for people like me (an engineer who uses code to get other work done). Thus, it seems that each time I want to explore a new feature of leo, I spend a bunch of time in trial and error trying to figure out how it works. A new user with other work to do just cannot justify the overhead required to do that. If there was up-to- date reference material available to quickly get going with different features, we would be much 'smarter' about using leo, much more likely to spread the word, and much more likely to contribute to its ongoing development. Terry said, much of the coolness of Leo is only relevant to at least somewhat technical users. I think we are relatively technical users, but still find it difficult. It may be a 'self-fulfilling prophecy' -- if the tool is complex to install, understand, and use, you will only attract the small audience of those with the time, energy, and skillset to work through it themselves. For 5.0, I would suggest focusing less on features and underlying architecture and much more of usability, ease of access for non-Python programmers, and comprehensive documentation of all core features, plugins, and dependencies. My 2 cents, Adam On Jun 18, 9:20 am, Edward K. Ream edream...@gmail.com wrote: 1. The goal is to increase the number of Leo's users. This is really the *only* goal. Leo is already good enough for what I do, so Leo 5.0 must focus on what others might want. Alternatively, we could skip 5.0 entirely, and concentrate on effective YouTube demos ;-) For example, here is the Code Bubbles demo:http://www.andrewbragdon.com/codebubbles_site.asp -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: Visions of Leo 5.0
Being able to run your data through a script is not a selling point for people who have no idea what a script is, so maybe one click install isn't critical. I respectfully disagree. One-click install IS critical for more widespread use of Leo. I don't understand why a user's knowledge (or lack thereof) of the concept of scripts would have any bearing on whether there should be a one-click installer. 1. The goal is to increase the number of Leo's users. PLEASE, before too much time and energy is put into Leo 5.0, PLEASE define what kind of new users you want? Who exactly is the target audience? What do you want/expect their technical skills to be? What problems can Leo help with that these users would appreciate? If you could make one of the goals for Leo 5.0 to be that it has less emphasis on its Python underpinnings and less emphasis on users needing to know something about Python to use it effectively, I think new users will get excited. Original Message Subject: Re: Visions of Leo 5.0 From: Terry Brown terry_n_br...@yahoo.com To: leo-editor@googlegroups.com Date: Saturday, June 18, 2011 7:37:03 AM On Sat, 18 Jun 2011 06:20:12 -0700 (PDT) Edward K. Reamedream...@gmail.com wrote: 1. The goal is to increase the number of Leo's users. This is really the *only* goal. Leo is already good enough for what I do, so Leo 5.0 must focus on what others might want. Not sure how this relates to points 2-5 :-) I think one click install would do more to increase the number of Leo users than anything else. OTOH, much of the coolness of Leo is only relevant to at least somewhat technical users. Being able to run your data through a script is not a selling point for people who have no idea what a script is, so maybe one click install isn't critical. It would certainly increase the number of people who try Leo, anyway. 5. Patterns (and other techniques) can define views. I think there's potential here but not sure if there's a single simple way of making views - not that you're suggesting there should be, but just pointing out that ways of generating them may be as varied as their uses. Which are not, of course, restricted to ways of looking at source code ;-) UNLs UNLs UNLs don't get anywhere near as much credit as they deserve. What does it stand for (have to branch contrib branch to find out... :-): Uniform Node Locators. Personally I think they can replace clones and eliminate all the complexity clones introduce, but I don't expect that to happen :-) I use leo/external/leosax.py to zip through a list of 20-30 .leo files and generate a view of all the todo nodes found therein. The script builds the view so that there's a node for each file searched, and below that a kind of sparse tree of all the todo nodes found in the file, which maintains the hierarchy among todo nodes, but ignores all others. E.g. if one file contained: A B C C1 D D1 D2 D3 D4 where A, C1, D, D1, and D4 where todo nodes, the resulting view would be node-for-file A C1 D D1 D4 with the priority of D adjusted to the max. of its own priority and the priorities of its descendants. Also, each node in the view is an @url node using an UNL to jump the user back to the original node in whichever outline. So: - don't forget UNLs - leosax can parse dozens of .leo files in seconds, the time is in building the view tree, not parsing the files. It does not expand @file nodes (which I don't use) - there are lots of kinds of possible views, of source, of summaries of .leo files as above, of database records, etc. - don't forget UNLs Cheers -Terry -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: Visions of Leo 5.0
On Sun, 19 Jun 2011 12:53:49 -0700 taa, Leo Newbie starman...@gmail.com wrote: Being able to run your data through a script is not a selling point for people who have no idea what a script is, so maybe one click install isn't critical. I respectfully disagree. One-click install IS critical for more widespread use of Leo. I don't understand why a user's knowledge (or lack thereof) of the concept of scripts would have any bearing on whether there should be a one-click installer. I was probably over-generalizing. A one-click install would be good for its own sake. Even for hardcore Leo users / coders it would sure be nice to be able to get it running on other machines that easily. And a one-click install would definitely increase the number of people who try Leo, which is obviously essential if we're going to increase user base, so yes, one-click install IS critical for more widespread use of Leo. My comment came from thinking that almost all the uses I make of Leo depend on at least simple scripts to glue stuff together. In a way that's not really true, seeing a lot of the time I'm just using it to write code, which doesn't require any scripting. If all you do is use Leo for writing code, I guess I don't really know how it stacks up against other environments, since the only other one I've used is Emacs, which I gave up for Leo. For me, the ability to script Leo, the python access to nodes, and the possibilities for non-coding uses etc. would make me choose Leo over other systems even if they were stronger on the coding aspect. But that's just me. I agree with aeromorrison that a period of user experience refinement would be good for Leo, it's just a question of people wanting to work on that. I'd like to work on the free layout stuff, the icon bar could probably be spiffed up, an installer would be nice, and a simple interface to the @auto / @nosent / @shadow / @file / @edit / @auto-rst would probably help a lot of people. Plugin management could also be refined. The documentation has improved, although to be fair I think it was always better than the average open source projects. But it could be improved more, particularly with respect to plugins and how users access the documentation (What's this? kind of tools). Perhaps we could have a little animated character which pops up and asks you what you're trying to do :-) Kidding. Maybe some bug-report / wish list items would be a place to start on some of this? Cheers -Terry -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: realpath in g.openWithFileName
On Sat, Jun 18, 2011 at 10:09 AM, Terry Brown terry_n_br...@yahoo.com wrote: g.openWithFileName needs fileName = g.os_path_realpath(fileName) at the start of it, otherwise g.openWithFileName(/home/tbrown/.leo/.todo.leo, c) will open another instance of an already open /mnt/usr1/usr1/home/tbrown/.leo/.todo.leo because it doesn't recognize them as being the same. Thanks for this. It's too late to put this in 4.9, but it will be in 4.9.1. Edward -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: wrong modality level on autocompleter?
On Sat, Jun 18, 2011 at 9:54 AM, Terry Brown terry_n_br...@yahoo.com wrote: Just noticed the autocompleter pop-up is modal globally, not just for the Leo windows. Probably should only block the Leo windows. Thanks for this. I'll put it on the list for 4.9.1. Edward -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
