Re: minor bugs
On Jun 10, 11:02 am, bobjack [EMAIL PROTECTED] wrote: 1: When you open a new leo frame from the menu, the new frame only has a single New Headline node. When you click that node another New Headline node appears. If you edit the first New Headline node the headline text of the second node changes as well. If you edit the second node the first node turns into and @chapters node. 2: If you start to edit a node then select another node then when you 'undo' it is the text in the currently selected node that is reverted not the node you actually edited. Bob Another minor bug is that when ctrl-shift-p is used to reformat a paragraph, all the coloring diappears. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: $200 reward for gui plugins
On Jun 10, 8:29 pm, Kayvan A. Sylvan [EMAIL PROTECTED] wrote: On Tue, Jun 10, 2008 at 08:21:46AM -0700, Edward K. Ream wrote: I agree. One of the biggest marketing blunders in Leo's history was to position Leo as a literate programming tool. Well, I would not have known about LEO if it weren't for the LP angle. I'm probably in the minority, however. Same here. Johannes --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: minor bugs
On Thu, Jun 12, 2008 at 4:55 AM, bobjack [EMAIL PROTECTED] wrote: Another minor bug is that when ctrl-shift-p is used to reformat a paragraph, all the coloring disappears. Thanks for this. The fix is on the trunk. This is the kind of nit that determines whether the new drawing code is, in fact, robust. In this case, there were two separate bugs: a bug in the reformat-paragraph logic (recoloring must be done even if the text doesn't change) and another bug in c.recolor (the wrong flag was being set). That real bugs were involved is good news: it means that there was not, in fact, any strange boundary condition that was causing recoloring not to happen. 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: minor bugs
On Thu, Jun 12, 2008 at 4:55 AM, bobjack [EMAIL PROTECTED] wrote: On Jun 10, 11:02 am, bobjack [EMAIL PROTECTED] wrote: 1: When you open a new leo frame from the menu, the new frame only has a single New Headline node. When you click that node another New Headline node appears. If you edit the first New Headline node the headline text of the second node changes as well. If you edit the second node the first node turns into and @chapters node. I don't see this with the present trunk code. Does it still happen for you? If so, what platform are you using? 2: If you start to edit a node then select another node then when you 'undo' it is the text in the currently selected node that is reverted not the node you actually edited. There is a problem with undo that can't easily be fixed. When editing a headline, Leo considers that any changes to the headline are not real until you actually end the editing. Furthermore, Leo can't easily tell when you are actually editing a headline (!) (The code is baroque) As a result, when editing a headline, if you do an undo you will a) revert to the previous contents of the headline *and* you do the previous undo. Yes, this sucks, but it's been this way forever and I'm not sure it can ever be changed. So if this is actually the problem I'm afraid you will have to live with it for now. 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Weave as rsT
I was victimized by my own tendency to avoid the read first, ask questions later principle. On Jun 5, 12:28 pm, derwisch [EMAIL PROTECTED] wrote: There is one function I am consistently missing. Maybe it is about time I scratch this itch myself. [...] Lacking these tools at my office PC, I would very much like to have a linearized document that has all comments rendered as restructured text and all code basically as is, wrapped in code tags, and processed according to whatever CSS I see fit. What do you think is the closest thing available in Leo to work from there? After reading the docs of the rst plugin and a bit of playing I found that the code-mode and show-doc-parts-as-paragraphs options make Leo do almost exactly what I want. Many thanks! --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: minor bugs
1: When you open a new leo frame from the menu, the new frame only has a single New Headline node. When you click that node another New Headline node appears. If you edit the first New Headline node the headline text of the second node changes as well. If you edit the second node the first node turns into and @chapters node. I don't see this with the present trunk code. Does it still happen for you? If so, what platform are you using? It is still present on my Windows XP and Vista machines, using 528. Leo Log Window... Leo 4.5 b1, build 1.244 , May 27, 2008 python 2.5.1, Tk 8.4.14, Pmw 1.3 Windows 5, 1, 2600, 2, Service Pack 2 --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: minor bugs
On Thu, Jun 12, 2008 at 8:26 AM, bobjack [EMAIL PROTECTED] wrote: 1: When you open a new leo frame from the menu, the new frame only has a single New Headline node. When you click that node another New Headline node appears. If you edit the first New Headline node the headline text of the second node changes as well. If you edit the second node the first node turns into and @chapters node. I don't see this with the present trunk code. Does it still happen for you? If so, what platform are you using? It is still present on my Windows XP and Vista machines, using 528. Oh. I see it now. It only happens when I use the File:New menu item. I'll fix this immediately. This will be another good test of the redrawing logic. 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: minor rclick issue
On Thu, Jun 12, 2008 at 8:14 AM, bobjack [EMAIL PROTECTED] wrote: On Jun 11, 3:51 pm, Edward K. Ream [EMAIL PROTECTED] wrote: On Jun 11, 8:44 am, Edward K. Ream [EMAIL PROTECTED] wrote: The little mystery of the missing redraw has been solved: cleo uses aMenu.add_command to invoke several commands. This is another way into code. add_command is used by several plugins, so I suppose changing m.add_command(...) to c.add_command(m,...) would be the way to handle this. I'll play with this today. rClick is broken by this. Sorry about that. I could have sworn I checked rClick specifically. I'll fix this today. No need to revert anything. 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Weave as rsT
On Thu, Jun 12, 2008 at 7:26 AM, derwisch [EMAIL PROTECTED] wrote: After reading the docs of the rst plugin and a bit of playing I found that the code-mode and show-doc-parts-as-paragraphs options make Leo do almost exactly what I want. Glad to hear it. rst3 can do almost anything as it is now. So much so that I never really am sure what it can do :-) 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: minor rclick issue
On Jun 12, 10:07 am, Edward K. Ream [EMAIL PROTECTED] wrote: rClick is broken by this. Sorry about that. I could have sworn I checked rClick specifically. I'll fix this today. No need to revert anything. The fix is on the trunk. All unit tests pass. Please let me know how it works for you. 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
