Re: r5148 can overwrite files on disk
On Saturday, March 17, 2012 2:26:55 PM UTC+2, Edward K. Ream wrote: > > On Fri, Mar 16, 2012 at 7:51 PM, zpcspm wrote: > > > I replaced "@thin code.py" with "@shadow code.py". > > Oh my. You are asking for loads of trouble do this. > My confusion about deleted content in code.py comes from the assumption that since I didn't modify the content of code.py explicitly - I was expecting leo to not modify it behind the curtain. I didn't use shadow files extensively, but I always saw creating shadow nodes as "symlinking" external files into an outline. Ok, it would be fine to get their content changed, but only if I would do it explicitly (which I didn't). Are these assumptions of mine flawed somehow? > Why not simply use the import command to recreate your code? > > > This option just didn't cross my mind, I have tried it now and here's my feedback: - leo added a "@language unknown_language" at the top of imported code.py, even if first line of it starts with "#!/usr/bin/env python". I am not sure this has any negative implications, since at least code highlight works and indentation wasn't broken - leo added the imported file as "@file" node with absolute path. I am a bit worried about how would this work for larger projects with multiple files. Wouldn't the outline structure get broken if the working directory is moved to another place (another directory, eventually another computer)? Of course this is pure speculation without trying, but after shooting myself in the foot once, I'd rather ask than try something else that "makes sense". - leo added the imported file as single node, didn't put each function into its own subnode I am still leaning towards trying the ugly hack instead (the one that I mentioned in my previous post). And I want to emphasize that this is not a feature request that should make leo work as I want in my particular case. I am rather trying to avoid getting a bad habit (replacing @thin nodes with @shadow ones), since this proved to be a wrong approach due to data loss. -- 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/-/JT_3pqN1UIoJ. 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.
r5148 can overwrite files on disk
I have just bumped into an unusual situation and I want to share it to get some feedback. I've opened an old pet project of mine (last commit was 2011-06-20 so it's been a while). It consists of a leo outline (let's call it outline.leo for convenience) + a src/ directory which contains a source code file (let's call it code.py) outline.leo has this in its header: https://groups.google.com/d/msg/leo-editor/-/11LqdELj3_UJ. 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: Whoosh, full text search status (bigdash.py)
On Sunday, March 11, 2012 11:40:49 AM UTC+2, Ville M. Vainio wrote: > easy_install Whoosh > > > Sorry for offtopic, may ask why are you using easy_install? Is it a developed habit or you have any particular reasons for installing third party python software this way? I am asking because I keep hearing good things about pip (though I've never started to use it yet, when I need a third party python thing, I usually build a package and install it using the package manager of my Linux distro). -- 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/-/h3Kz_WZOcdcJ. 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: I'm in bzr pain
On Saturday, March 3, 2012 12:49:25 PM UTC+2, Edward K. Ream wrote: > > On Fri, Mar 2, 2012 at 11:01 PM, tfer wrote: > > Dang, I'd bound leo to trunk, I see that the head is now trunk3, no > > wonder I wasn't able to pull latest. > > Glad there was a simple fix. I think the safe way is to use lp:leo-editor. > This of course works for branching, but for updating a local copy `bzr pull` is just enough, initial branching location seems to be stored and is used by default. Maybe there's a way to lock somehow that outdated branch on launchpad so that bzr client would throw some explicit error when people who missed that change on launchpad will still try to pull from it? -- 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/-/ScF2RYeTLp8J. 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: I'm in bzr pain
On Friday, March 2, 2012 8:05:53 AM UTC+2, tfer wrote: > > > Anyone else having problems with Launchpad? > > IIRC there was a thread about this some time ago, but it was related only to memory problems when running bzr in Windows. Just did a test branch from launchpad: $ time bzr branch lp:leo-editor Branched 5054 revision(s). real2m20.692s user0m42.054s sys0m1.153s Here's some details about my setup to match against: slackware linux 13.37 (64bit) bzr 2.3.0 (vanilla, built from source) python 2.6.6 python process that ran bzr took max 130 MB of RAM while working peak download speed from launchpad was 1Mbps -- 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/-/oAqt8bZdSLkJ. 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: Recommended video
On Feb 21, 2:31 pm, "Edward K. Ream" wrote: > Adding Richard Stallman to the > list of "crusaders" could be called truth in advertising, I'll give > him that. RMS is rather a prophet to me. Ironically, I failed to watch the video because my OS is flash free and Firefox doesn't seem to support h264 by default. After wasting like 30 minutes googling I gave up. -- 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: Aha: simple refactoring commands
On Jan 30, 9:16 pm, "Edward K. Ream" wrote: > Renaming ivars, methods or classes is one of the most important kinds > of refactorings. > > I just realized that a relatively simple change will turn Leo's find/ > change commands into a rename command. The differences are: > > 1. Might be non-interactive. > > 2. Will check before making any changes in a node that the replacement > string does not already exist in the node. > > A *safe* find/replace would be a very important tool. For example, I > would like to make the types of lists more explicit by changing aList > to si_list, in those places where aList does, in fact, contain nothing > but ShortcutInfo nodes. > > Edward While find/replace it is used to rename variables/class methods - it is not refactoring per se - it is just a string operation, a technical tool that is used to achieve a goal (this final goal being refactoring). Did you try rope for this? I've never used it for such big and complex codebases like leo, but for small pet projects (single source code file) it does the job. -- 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: Making the docs more open to community contributions
On Jan 5, 8:25 pm, Terry Brown wrote: > The barrier to contributing to the docs. is knowing how to use bzr to > push to the trunk And also having a minimum amount of knowledge about rst -- 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: clone outline window
This is a valid request. A couple of years ago I had to deal with a big outline where massive node management (copying/moving/cloning) operations were required. I ultimately did everything manually, but it required a huge amount of scrolling back and forth through the outline pane. I didn't post to group then for many reasons: - I am trying to make a suggestion / request a feature only after I bump into a problem at least twice. Sometimes I would try to do something with leo, fail to achieve my goal and abandon it. However, after a while I'm eventually back trying again. This may take a couple of months though, but meanwhile I learn a thing or two more about leo which sometimes helps progressing. - I am the guy who contributes not that much to this group and unfortunately almost doesn't contribute to developing leo at all. So I don't think it's fair to ask lots and give back much less. But I try pulling the trunk on a daily basis and read the group. I can see the titanic work Edward does every day and I avoid bothering him too often with my minor issues :-) But leo is evolving, it becomes better, it moves into the right direction constantly and this is enough to keep me happy. However, this is a good place to estimate if there are many people in the leo community who may need a particular feature implemented. Two outline panes would certainly come handy in specific situations when big amounts of copy/move/clone node operations are needed. Two pane file managers are still a whole era in user interfaces, there's no conceptual difference between a filesystem and a leo outline after all. Think of norton commander/dos navigator/total commander/midnight commander (I happen to still use last one on a daily basis and I am very happy with it). -- 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: terminal window
I'm not absolutely sure, but I think pida - the python IDE - used to have a terminal window. Maybe builtin, maybe a plugin. However, it's python code so you may try looking there. -- 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: Anyone know of advantages or disadvantages of new-style classes?
I know for a fact that method resolution order for new style classes is different (but not well enough to be able to explain it, I just try to avoid mixing old style classes with new style ones for this reason). Without knowing any details about the appeared problems that you mention, I wonder if that difference may be the reason of issues. -- 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: New html import code on the trunk
On Nov 11, 11:49 pm, "Edward K. Ream" wrote: > The code at rev 4776 imports the infamous data.html file correctly. > All unit tests pass, but there is the potential for unintended > consequences. As always, please report any problems immediately. I have noticed a problem: there's still some nodes with wrong content in the body. One of them is easy to spot if you search the outline for string '' after importing data.html and see the last match. This is the beginning of a 'tr' node. Perhaps you could add a test that looks for '' at the end of each node body. It shall be case-agnostic, at least for HTML tags and hopefully will catch more edge cases like this. -- 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: Any leo plugin that can import HTML code into a tree?
On Nov 9, 11:02 pm, "Edward K. Ream" wrote: > On Oct 28, 2:49 am, zpcspm wrote: > > > Sometimes I have to look at badly aligned HTML code and keep asking > > myself questions like "here's the opening tag, I wonder where it > > closes". > > To be clear, rev 4767 imports data.html properly. > > Edward Thanks for your work on this, Edward, I am using the same data.html that I've sent you as reference and after updating leo to r4767 the import looks much better. However, I still can see some glitches, so I'd like to check maybe I am missing something. So, importing the file creates a bigger outline with more nodes as tags - this is the good part. There's still nodes with wrong content in body. For example I get a node with head "p" and body: @others It has a child node with head "div" and body: List of Non-Compliant Issues It looks like leo still makes a difference between lowercase and uppercase tags when importing HTML. My next step was to copy the setting @date import_html_tags from leoSettings.leo to myLeoSettings.leo and double its content by appending the whole list of tags in uppercase one more time (just in case if I'm expected to do that) and try importing data.html again. I have restarted leo completely before importing again, to make sure changes from myLeoSettings.leo would get considered. Results are still the same - some nodes don't have adequate values in their bodies. Other problems I have noticed in this setup: - for some reason there's a "data declarations" node which contains in body. - there's no "body" node, for some reason tag is inside a "script" node. It is easy to find this if you search the outline for "http://groups.google.com/group/leo-editor?hl=en.
Re: Any leo plugin that can import HTML code into a tree?
On Nov 3, 12:06 am, "Edward K. Ream" wrote: > 4. html often will contain javascript code that has its own syntax > rules. I'm not sure this makes any difference, actually. I am not sure either, isn't javascript supposed to be always wrapped in a
Re: Any leo plugin that can import HTML code into a tree?
On Oct 29, 7:57 pm, "Edward K. Ream" wrote: > On Sat, Oct 29, 2011 at 6:28 AM, Edward K. Ream wrote: > > >> error: import command did not import @file data.html perfectly > >> first mismatched line: 272 > > [snip] > > > Somehow the second line uses Leo's strange -4 convention for > > representing underindented lines. > > Please send me a small .html file that exhibits this error. Done. -- 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: Any leo plugin that can import HTML code into a tree?
On Oct 28, 2:12 pm, "Edward K. Ream" wrote: > On Oct 28, 3:49 am, zpcspm wrote: > > > Is there a leo plugin that would automatically solve this by being > > able to import HTML code into a tree of HTML tags - one node per tag, > > inner nodes for inner tags? Something like this: > > Leo's import command works with html files. It will generate nodes > for the tags mentioned in the setting: > > @data import_xml_tags > > Edward 1. Why are there redundant values (uppercase and lowercase) in this setting? I know that XML tags are case sensitive, but HTML tags are not. Having to double each HTML tag is slightly inconvenient. 2. Is it possible to have an alternative value for this setting (commented, so it won't interfere with the default one) in leoSettings.leo, that would contain all HTML tags? I can probably google this list of tags, but I'm confused by the inconsistency between the setting name (it's about XML) and the default tags (HTML ones!). Maybe it would make sense to have a distinct setting for HTML tags? I understand it would add redundancy, but HTML is a very big particular case. 3. I've tried to import a file and got some warnings: warning: intermixed blanks and tabs warning: mismatch in leading whitespace first mismatched line at line 95 original line: generated line: error: import command did not import @file data.html perfectly first mismatched line: 272 270 u'\t\t\t\n' 270 u'\t\t\t\n' 271 u'\n' 271 u'\n' 272 u'\t\t\t\t\t\n' 272 u'-4\t\t\n' 273 u'\n' 273 u'\n' 274 u'\n' 274 u'\n' 4. The import algorithm for HTML doesn't seem to be perfect. For instance, I have a node with the following body: (as of the previous business day) This looks wrong. -- 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.
Any leo plugin that can import HTML code into a tree?
Sometimes I have to look at badly aligned HTML code and keep asking myself questions like "here's the opening tag, I wonder where it closes". Is there a leo plugin that would automatically solve this by being able to import HTML code into a tree of HTML tags - one node per tag, inner nodes for inner tags? Something like this: header content: body content: @others # all inner tags here I could probably use firebug for this but I try to avoid it because it is slow. -- 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: OT: pycallgraph
On Oct 27, 10:36 pm, "Edward K. Ream" wrote: > Yes. pycallgraph is cool. Back ago I've got stuck with a scenario in which I threw a huge class to pycallgraph and it choke when trying to chew it out: there were so many method boxes on the resulting image that the text in them was totally unreadable. IIRC I tried to change output formats, always with same result. Of course a huge class is always a design antipattern, but I was trying to use pycallgraph to actually refactor it, and it failed to help (or I failed to use it properly). If any of you went through this and found a workaround, I'd be happy to read about it. -- 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: leo & (g)vim
On Jul 4, 8:17 am, Gour-Gadadhara Dasa wrote: > Hello, > > I wonder what's wrong with my installation (rev #4413) that I get option to > edit nodes with vim and not gvim? > Is this the default behavior? I've had success to change the external editor to gvim/scite by setting an explicit value to LEO_EDITOR env variable (in Linux). I have gvim installed, LEO_EDITOR=/usr/bin/gvim (note the full path, a good habit, borrowed from writing scripts for cronjobs, to avoid most PATH related issues) and I can edit nodes in gvim. Just tried it for current trunk of leo - r4413 as well. -- 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: Feature request: leo should be able to load icons from a custom location
On Jun 14, 8:36 pm, "Edward K. Ream" wrote: > I'll put it on the list. Is there is some reason why > you can't replace the box icons yourself? On Jun 14, 9:54 pm, "Ville M. Vainio" wrote: > If you are running from bzr branch that you update regularly, > replacing files will cause problems. Better have the "user specified" > stuff outside the source tree (as is the case w/ myLeoSettings.leo) Exactly. This is my use case. I can replace the genuine icons that come with leo, but as soon as I'll pull from launchpad - a merge conflict will happen. -- 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: Heads up: leoSettings.leo reorganized. 9 settings removed
Perhaps leo could also have a command to validate myLeoSettings.leo and complain if it finds some obsolete settings that got removed from leo, but are still present in myLeoSettings. A special case would be to validate enabled-plugins node too, which can sometimes contain legacy lines, like it recently happened with UNL plugin that got moved to cotrib branch. -- 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: Tk is now gone.
On Jun 4, 3:49 am, "Edward K. Ream" wrote: > On Fri, Jun 3, 2011 at 6:01 PM, lewis wrote: > > I still see this traceback > > reading: C:\Python31\Lib\site-packages\leo-editor\leo\doc\LeoDocs.leo > > Oops. An @enabled-plugins node contained UNL.py. Actually, there is > no longer any need for this node at all, imo. > > Thanks for this report. The fix is at rev 4262. > > Edward Such tracebacks can be user-specific as well. I've got the same because I had UNL.py enabled in myLeoSettings.py. I just deleted the line and restarted leo. -- 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.
Feature request: leo should be able to load icons from a custom location
Problem: leo's "boxXX" icons are hardcoded. They don't look too well if leo runs with a dark theme. Please see http://i.imgur.com/dkVjp.png I think leo should be able to load icons from a non-default location. This way it would be possible to use another set of icons instead of default ones. Perhaps ~/.leo/ is a good candidate, leo could look there for an Icons subdirectory and load icons from there first, then fall back to default ones. -- 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: Regarding bug #323967
On Jun 3, 2:44 pm, "Edward K. Ream" wrote: > On Thu, Jun 2, 2011 at 1:44 PM, zpcspm wrote: > > @color body_text_background_color = #00 > > @color body_text_foreground_color = #ff > > Leo starts with black background in body pane, switches to pink as > > soon as mouse wheel is activated. > > Looking at the code, these settings are the default background colors > for the various mode colors: command_mode_bg_color and the other color > in @settings-->Colors-->Body pane colors. > > I don't see color flashes with the default settings, but it's probably > not a bad idea to set the various mode colors explicitly. I just copied the whole "Body pane colors" subtree into myLeoSettings and changed all foreground/background pairs to white/black. No more flashing. There was a color clash: in code snippets, operators were invisible because of "@color operator_color = black" setting. I tried to "cheat" and change it to None, hoping that it'll inherit the default foreground color, but that didn't work. I don't know if this qualifies as a bug or not. However, changing that setting to "@color operator_color = white" made operators visible. I'm almost happy, there's only one rough edge left. But I think it deserves its own topic, so I'll continue there. -- 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: Regarding bug #323967
On Jun 2, 9:39 am, zpcspm wrote: > This is next to be investigated deeper in my TODO. 1. set @color body_text_background_color = #00 @color body_text_foreground_color = #ff in myLeoSettings.leo and restart. Leo starts with black background in body pane, switches to pink as soon as mouse wheel is activated. 2. print-settings is useful for debugging (it's better than nothing), but it's still not enough 3. help-for-command print-settings says "no docstring". I know about it only because I was told about it. I don't know how easy is for somebody to discover this command himself. Perhaps a docstring should be added. 4. doc for body_text_background_color says "this setting can be overridden by the x_mode_bg_color settings". Since leo changed background (see 1.) I suppose this is exactly the case. But from the output of print- settings I don't understand which x_mode_bg_color setting was body_text_background_color overriden by. It would be great if print-settings could dump something like: setting_foo (overridden by setting_bar) instead of: setting_foo setting_bar 5. To make it easier to investigate settings, perhaps print-settings could be modified to accept a filter argument, like: print-settings *color which would print only setting names ending in "color". This is a detailed description of a failed minimal attempt. Should I just keep guessing and try changing other options? Is there a better way to get custom colors in the body pane? -- 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: Regarding bug #323967
> > > Also, I still don't know how to change the style of the splitter (it
> > > stays blue while I want it dark).
>
> Changing this item in the @data qt-gui-plugin-style-sheet node works
> for me::
>
> QSplitter::handle {
> background-color: #CAE1FF; /* lightSteelBlue1 */
> }
>
This worked.
> As of rev 4212 the mod_scripting plugin no longer sets colors of
> buttons.
As consequence buttons inherit by default the current style and look
well.
> > > Are the color settings in "leoSettings.leo-->@settings-->Colors-->Body
> > > pane colors" documented somewhere?
>
> > Good question. They should be documented in leoSettings.leo, in the
> > node you give.
>
> Actually, they are documented in each individual @color node. I
> suppose the setting name is supposed to be self-explanatory :-) Let
> me know if you have specific questions.
This is next to be investigated deeper in my TODO.
--
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: Regarding bug #323967
On May 22, 8:21 pm, "Edward K. Ream" wrote: > On Sun, May 22, 2011 at 9:28 AM, zpcspm wrote: > > So is there another bug regarding custom colors in themes that I could > > watch or does it need to be created? > > There is no bug. The colors are created by settings. See leoPy.leo: > @settings-->Colors-->Body pane colors > > Edward Are the color settings in "leoSettings.leo-->@settings-->Colors-->Body pane colors" documented somewhere? I've quickly scrolled through http://webpages.charter.net/edreamleo/coloring.html but couldn't find anything relevant there. I had a short "trial/error" attempt to modify those settings (still trying to build a dark theme for leo), I managed to get a dark background in the body pane, but during mouse scrolling (even for an empty body pane), it was blinking (like it was applying the default pink background then the black background again). Also, I still don't know how to change the style of the splitter (it stays blue while I want it dark). Command buttons in the toolbar look ugly as well (yellow and blue). -- 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.
Leo's home page confused me :-)
I'm about to look for something in Leo's docs, so I went to http://webpages.charter.net/edreamleo/front.html I didn't visit that site long enough to forget how it looks. I still remember the old, pre-sphinx generated site (because I used to go there more often). Nowadays I'm mostly using a keyboard driven window manager and I generally use keyboard only for browsing as well. I searched the page for "toc". 0 matches. I searched for "manual". 0 matches. I panicked, grabbed the mouse and started to click those links on the left and ... didn't find the manual. Then I accidentally put the mouse cursor on the lion and saw it's clickable. I clicked and found the manual. I switched tabs and started to type this post. Before submitting I looked at Leo's homepage once more and I saw the header and the footer. Two more links pointing to the user manual that my brain completely overlooked, perhaps because they have a different background and that predominant yellow background attracted my attention more. Moral of the story: Leo has at least one user who managed to get confused by it's home page. I expected to find a link to the manual among those links on left. -- 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.
Multiple tracebacks when activating menu items
leo r4153 Slackware Linux 13.37 32bit Python 2.6.6 qt-4.7.0 PyQt-4.8.1 exception updating Outline menu Traceback (most recent call last): File "/tmp/leo/leo/core/leoMenu.py", line 153, in updateOutlineMenu enable(menu,"Cut Node",c.canCutOutline()) File "/tmp/leo/leo/plugins/qtGui.py", line 5825, in enableMenu if s.startswith(name): AttributeError: 'QString' object has no attribute 'startswith' exception updating Edit menu Traceback (most recent call last): File "/tmp/leo/leo/core/leoMenu.py", line 99, in updateEditMenu c.undoer.enableMenuItems() File "/tmp/leo/leo/core/leoUndo.py", line 1011, in enableMenuItems frame.menu.enableMenu(menu,u.redoMenuLabel,u.canRedo()) File "/tmp/leo/leo/plugins/qtGui.py", line 5825, in enableMenu if s.startswith(name): AttributeError: 'QString' object has no attribute 'startswith' exception updating File menu Traceback (most recent call last): File "/tmp/leo/leo/core/leoMenu.py", line 84, in updateFileMenu enable(menu,"Revert To Saved", c.canRevert()) File "/tmp/leo/leo/plugins/qtGui.py", line 5825, in enableMenu if s.startswith(name): AttributeError: 'QString' object has no attribute 'startswith' exception updating Edit menu Traceback (most recent call last): File "/tmp/leo/leo/core/leoMenu.py", line 99, in updateEditMenu c.undoer.enableMenuItems() File "/tmp/leo/leo/core/leoUndo.py", line 1011, in enableMenuItems frame.menu.enableMenu(menu,u.redoMenuLabel,u.canRedo()) File "/tmp/leo/leo/plugins/qtGui.py", line 5825, in enableMenu if s.startswith(name): AttributeError: 'QString' object has no attribute 'startswith' -- 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: Leo now uses a splash screen: non-copyrighted image needed
On May 26, 5:41 pm, "Edward K. Ream" wrote: > As of rev 4148, Leo will put up a splash screen while loaded. > > I like this a lot, but you can disable the feature by removing leo/ > Icons/SplashScreen.jpg. I would like to point that this isn't the best approach (even if it seems to be the simplest). For example, for people running leo straight from its repo (I am one of them) removing that file would mean altering the repo. Please consider to add a config setting for this which could go into myLeoSettings. I think this is the lightest possible way to add flexibility (a command line argument for this would probably force those people who run leo via custom shell wrapper scripts to change them). -- 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.
Regarding bug #323967
Edward, I confirm that the recipe you suggest there works. I can manipulate these @color settings to get non-default colors for the minibuffer. I also agree that a comment in "qt-gui-plugin-style-sheet" setting node is good to have. However, the very first message in bug report links to http://groups.google.com/group/leo-editor/browse_thread/thread/9005aa942d770dfa and last post there says "This bug will be where the theme-related issues get addressed." Now the minibuffer can be tuned, the bug is marked as invalid, but there are still theming issues with the body pane. For example, if I open a leo outline, the body background is black (I tell it to be black in my custom stylesheet). As soon as I activate the mouse wheel to scroll the body, leo overwrites the colors and I get the pink background again. So is there another bug regarding custom colors in themes that I could watch or does it need to be created? -- 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: The highlights of my workflow
Looks good. Do you also have any bzr specific gotchas that you plan to add to this section? -- 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: Completer look tweaked
On May 17, 7:53 pm, Gour-Gadadhara Dasa wrote: > On Tue, 17 May 2011 07:54:44 -0700 (PDT) > "Edward K. Ream" > wrote: > > > Thanks for this detailed report. I'll fix it immediately. > > You're welcome. Do you prefer that (next time) new ticket is opened > at LP or reporting here is also acceptable? I think discussing here is ok. Eventually a bug is acknowledged and a bug report is added to LP. Sometimes things that go wrong are related to already existing LP bugs. Having a preliminary talk here adds a bit of redundancy but keeps the LP bug reports laconic and purely technical. Eventually, a group thread and a LP bug report are crosslinked to make it easier to remember the context. Disclaimer: this is purely my point of view. I'm watching this group closely and this is how I see it happening. -- 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: How to tell leo it should not put its icon into systray?
On May 16, 5:20 pm, "Ville M. Vainio" wrote: > Disable systray.py plugin Thank you. I've added it myself but I forgot I did that, I even forgot it's a plugin, not a part of qtGui that can be toggled using a setting. git annotate myLeoSettings.leo shows it was me. -- 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.
How to tell leo it should not put its icon into systray?
Topic title says it all. I've recently started to learn xmonad and apps that put icons into systray when I start them are interfering with my newbie workflow. I am always using the current trunk on Linux, I don't remember all details, just that one day leo started to display an icon in the systray. I never interact with it so I'd rather have leo not dealing with the systray at all if this is possible. -- 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: Font size in Leo
On Apr 18, 6:21 am, Terry Brown wrote: > @data qt-gui-plugin-style-sheet This is correct for the qt GUI, which is the default one. If you happen to use the old tk GUI, there were other settings for font name and size. -- 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: Managing 'to do' lists in Leo / @language colorizer for 'to do' lists
leo has a TODO plugin named todo.py, do you know about it? IIRC it's not enabled by default, but enabling it is a matter of having an uncommented "todo.py" line in @enabled-plugins inside your myLeoSettings.leo file. todo.py is a port of cleo.py, todo.py is for the qt GUI, cleo is for the older tk GUI. -- 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: Revision 3862 crashes for me on startup
I believe this is due to qt-4.5, because I recall a similar error in another context: https://groups.google.com/group/leo-editor/browse_thread/thread/a391902cd38e2d42/8955d1e7942e76d8 -- 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: Globally available functions
On Feb 23, 11:19 pm, Court-Jus wrote: > My relationship with leo is currently changing from "friendly" to > "intimate", I use it everyday at work for many purposes (mainly todo > lists and activity reports). I've created some buttons to help me but > I've duplicated many functions (copy/paste) in every on of these > buttons. > > I didin't find how to put in a node or tree some "helper" functions > that I need everywhere. > > Can anyone point me to the light ? If you have multiple buttons sharing duplicated code in the same outline, an option is to use clones for having the common code in @button subtrees. But I'm not sure this is the right approach or the best approach. Since you're scripting leo, I assume your code is written in python. If you are looking to eliminate duplicate code and are not aware of Clone Digger (http://clonedigger.sourceforge.net/) yet, you might give it a try. -- 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: Please run Python 3k unit tests before commits
On Feb 23, 4:48 pm, "Edward K. Ream" wrote: > > I can attempt writing a mini-FAQ that would be developer oriented. I > > write the questions, comments for the questions (not answers to the > > quesions, because I don't know them!), the FAQ gets reviewed, > > Good idea. Let's do it in this thread. Here is the mini-FAQ as leo outline. Can't figure out how to attach the file to my post and I remember google doesn't always play nice with xml pasted as text, so here's an external link. http://dl.dropbox.com/u/4226858/dev.leo (5503 bytes) PS: please let me remind you that English is not my native language, so the content may be not ideal. Feel free to ask for comments. -- 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: Please run Python 3k unit tests before commits
On Feb 22, 4:36 pm, "Edward K. Ream" wrote: > On Wed, Feb 2, 2011 at 9:44 PM, zpcspm wrote: > > Did you consider to have a > > distinct chapter for developers (even if it would be in "Leo’s Users > > Guide", not in "Leo’s Developers Guide")? > > Good idea. Would you like to write it? :-) I wonder how could I write about your workflow which I don't know in details :-) Hence my idea about having a chapter exactly for that. But I think I understand what you mean. You are basically in the same situation. While you know your own workflow, because you practice it a lot and don't have to write it down for reference, you are subjective in understanding the issues of people who superficially follow leo (like me) or who are totally new to it. Hence: > Or suggest topics of interest to you? I can attempt writing a mini-FAQ that would be developer oriented. I write the questions, comments for the questions (not answers to the quesions, because I don't know them!), the FAQ gets reviewed, completed and you use it as reference for writing the new chapter. So basically having those questions answered will get us a new chapter and the FAQ itself will serve as glossary for it. -- 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: Continued Tk support
On Feb 11, 9:26 pm, Ethan Furman wrote: > Whew! > > At long last, the three patches I created have been committed to trunk. > > Unfortunately, Trunk won't run on my (Tk-based) machine (even before I > put my patches in). > > I seem to recall a post somewhere questioning further Tk support in Leo > -- was a decision made on this issue? > > ~Ethan~ r3853 of leo runs for me with Tk GUI. It also opens an existing outline. You should provide more context about your setup. Here is mine: Slackware Linux 13.1 Python 2.6.4 Tk-8.5.8 leo version is above Also, run leo from a terminal (launchLeo.py --gui=tk) to catch any eventual tracebacks. -- 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: Please run Python 3k unit tests before commits
On Feb 2, 6:30 pm, "Edward K. Ream" wrote: > A common mistake for new committers is to forget to make the code > compatible with Python 3k. The first step before any commit is to run > all the unit tests in unitTest.leo with Python 3k. This will catch > all Py3k syntax errors at the very least. > > Edward I just opened http://webpages.charter.net/edreamleo/leo_toc.html and had a quick look. None of those chapter names seemed to be related to the issue that you are bringing up. Did you consider to have a distinct chapter for developers (even if it would be in "Leo’s Users Guide", not in "Leo’s Developers Guide")? You're crafting leo for years, I bet you follow a certain workflow instinctively, so you can't forget it and you know all the gotchas (like reference files, which new potential contributors can not be aware of or just need a place to look for until they remember it, like tests that have to be run before commits, like python 2.x and 3.x compatibility, like the presence of multiple GUIs, which implies it would be good to run those tests in both qt and tk to keep them both healthy while tk is still supported). Some related things to the development of leo itself are in the "How should I use Leo with bzr/git/hg/svn/cvs?" FAQ entry, this can be mentioned in the new chapter too. You could as well provide more details about environments that you are using. For example, I follow this group for a couple of years and I don't know if you're using something like virtualenv or not. Actually, I mean I can't remember if this was ever mentioned here or not. Another example: it's been a couple of months since I ran leo's tests for the last time (perhaps because it didn't gave me issues lately, which is good), so I don't remember anymore how to do it. I know there are some commands for it, I know there are Alt-Digit bindings for these commands that you usually mention and I overlook when I read the new posts (because I pay more attention to keywords and tend to miss details). My point is: just document your own workflow in a distinct chapter and let other people follow it step by step. -- 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: Leo ToDo plugin documentation missing
On Dec 15, 12:01 am, Ivanov Dmitriy wrote: > Onhttp://webpages.charter.net/edreamleo/plugins.html#todo-pythere > are 2 links: > > http://leo.zwiki.org/ToDohttp://leo.zwiki.org/tododoc.html > > Then all lead to a missing page. Can someone, having the docs, put > them into a robust location? todo.py is a port of cleo Tk plugin to qt, you might also find this useful: http://leo.zwiki.org/cleodoc.html It is oldish, but at least it's better than nothing. Since I know about cleo for a couple of years, it is no problem for me. Yet this inconsistency is perhaps inconvenient for first time users. Maybe renaming those plugins to something like todo_tk.py and todo_qt.py would be more intuitive? Of course this would break backward compatibility, because people using these plugins would have to adjust their leo settings to reflect the changes in plugin names. But maintaining the status quo just keeps the distance between these two plugins bigger than it should be. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: quicksearch is not working as expected
On Dec 10, 5:36 pm, Raj wrote: > Is it recommended to stay with Py 2.x series then? Yes. And this is not leo-specific. It is common sense for most python related software. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: How to run bash script within Leo node?
On Nov 23, 10:00 pm, smcho wrote: > I have @file runme.sh node to generate a bash script to do some > actions. > > Normally, I open console to run the runme.sh, but can I run runme.sh > inside Leo? you could write some python code that uses the subprocess module (the modern replacement for os.system()) and runs the shell script -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Running python script with Leo node.
On Nov 23, 9:57 pm, smcho wrote: > I learned that I can write down python code in a Leo node, and use > command-b to run the script. > > It seems to work well, but when I tried to print something, I had to > use g.es() not print(). > > * Why is this? Some of the python functions are not available in leo > node? print or print() in python3 prints to console if you run leo from a terminal, you'll see it there g.es() prints to the log panel IIRC -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Is something basic missing from Leo?
If you are eager to try this collaborative workflow without leo, feel free to have a look at Gooby (http://gobby.0x539.de/trac/) -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: ANN: "tabula" command added to stickynotes plugin
On Nov 19, 6:19 pm, Offray Vladimir Luna Cárdenas wrote: > I'm using Leo 4.7.1 on Linux and have opened myLeoSetting.leo -> > @enabled-plugins where I enabled bookmarks.py but there is not anyplace > where I can find stickynotes.py Is this plugin available for this > version of Leo?, Could plugins be downloaded and installed without > bazaar knowledge? (I will learn it but if is needed, but I'm thinking in > a non programmer/"Techie" user of Leo). Sometimes plugins get added to the codebase, but don't make it into @enabled-plugins of default leoSettings.leo immediately. Your best bet is to study the plugins directory and add the enabling line manually to @enabled-plugins (instead of uncommenting it for plugins that are present there by default). -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Leo looks ugly and inconsistent with a dark Qt theme
On Nov 13, 9:51 pm, zpcspm wrote: > Some parts of the colorized body text are not visible as well, looks > like a clash between my custom black background and the color used for > certain patterns by leo. A partial workaround is to use @nocolor in node bodies. Thus my dark- themed leo becomes suitable for taking notes but not fully suitable for coding yet. This makes me wonder if it is possible to tell leo "use @nocolor for the whole current outline" without having explicit @nocolor directives in node bodies. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Leo looks ugly and inconsistent with a dark Qt theme
I did some tweaking to the qt CSS, here is my current progress: http://i.imgur.com/9RBGO.png Besides the mentioned problem with the minibuffer background, there are some more. I couldn't find anything related to the script buttons in the style sheet. If by any chance mod_scripting initializes them using hardcoded values for colors and fonts, it will be good to have these settings in the style sheet too. Even if mod_scripting is a plugin, it is a very important one and it is enabled by default. Some parts of the colorized body text are not visible as well, looks like a clash between my custom black background and the color used for certain patterns by leo. Text selection in body is decent: http://i.imgur.com/wgeCj.png -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: New plugins chapter is ready: please review
Here are a couple of ideas. active_path.py Synchronizes @path nodes with folders. at_folder.py Synchronizes @folder nodes with folders. I have doubts this is clear for a newbie. Plugin docstrings shouldn't be too big, but I think they should provide a bit more context. Often people are looking for plugins because they have a certain task they want to solve in mind, it will be good if plugin docstrings will provide some hints about the problems that can be solved using these plugins. Additional confusion comes from these two docstrings being very similar, it is not instantly clear what is the difference between these two. add_directives.py Allows users to define new @direcives. I suppose "direcives" is a typo here. cleo.py Creates coloured LEo Outlines. I'm not sure "LEo" looks good. "Leo" or "leo" looks better. Also, leo is the "TODO" plugin for Tk, I think this is worth to be mentioned in the summary. It is good to mention as well that this is the equivalent of the qt "TODO" plugin called todo.py contextmenu.py Defines various useful actions for context menus (Qt only). While this might be redundant with the "Content" tree above, I think it is a very good idea to have a "(Qt only)" or "(Tk only)" explicit note at the end of each plugin in the Summary list. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Leo looks ugly and inconsistent with a dark Qt theme
I might try to play a bit with colors in qt-gui-plugin-style-sheet setting in the near future to see if there is some potential for improvements there in the context of my scenario. Is it possible to reload the modified content of myLeoSettings and have leo automatically apply the updated stylesheet to its GUI without explicitly restarting it? -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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.
Leo looks ugly and inconsistent with a dark Qt theme
First, I will provide a bit of context. I'm currently experimenting with creating an eye-candy dark-themed desktop. I'm using Linux, but I'm not using GNOME or KDE. Currently, my setup consists of: - a dark fluxbox theme (fluxbox is my window manager of choice) - a dark gtk2+ theme - a dark gkrellm theme (gkrellm is a system monitor) These play well together and look good. The missing piece of the puzzle are qt GUI apps. It is possible to make them use the gtk theme with gtk-qt-engine. Here is how a qt app (qbittorrent) is looking with it: http://i.imgur.com/7pPcM.png Now here is leo: http://i.imgur.com/63mfJ.png I see many problems here: - there are a lot of places where the gray color looks unreadable due to a hardcoded (probably that qt CSS template from leo settings) light background: the button labels, the tree headlines, the minibuffer, the status line - there's some void white background behind the multitabbed log panel - the splitter color is not consistent with the dark theme, I would expect it to be dark as well - the dark theme interferes with the hardcoded color values used by the colorizer, see those hardly readable "python" and "main()" in the body panel For comparison, see how gvim is looking: http://i.imgur.com/Oaezf.png gvim is a gtk app, so this last screnshot illustrates two points: - the look of qt and gtk apps stays consistent (this is good) - the look of gvim and especially the code in gvim is much more eye- candy than in leo. Normally, I wish that leo could look like gvim by default Ideally, there will be some feedback on this rant of mine here and probably a wishlist bug will be filled at launchpad then. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Not "Literate Editor with Outlines", so what is Leo?
Why not keeping the package description in sync with what is displayed on leo's homepage? "An outline-oriented browser and project manager" looks good to me. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: fcol bug?
On Nov 5, 5:05 pm, tfer wrote: > Now I may have an imperfect grasp of "fcol" as displayed in the lower > left hand corner, but isn't it intended to show what column the > current body text cursor would be at in the externally generated > file? This is correct. I was the one who made this request. And I was the one who implemented it (after posting details on this group, here is the relevant thread http://groups.google.com/group/leo-editor/browse_thread/thread/6f744c2a5819e3). This feature was introduced with r899.1.1, there are also a couple of unit tests in leo/test/unitTest.leo (UNL "All unit tests-->Organized by file-->leoNodes-->tests for p.textOffset()-->@test node that doesn't belong to a derived file"). > The bug I noticed has can be seen in the first example, i.e. > the @@thin node. p.textOffset() is using isAnyAtFileNode() to find out if the parent of a node is the root of an external file subtree. isAnyAtFileNode() behaves differently for "@thin" and "@@thin", I think this is the problem. As I understand, "@@" is used to escape the directive so the external file won't get actually created (but the meaning is still the same - this is a node that serves as root for an external file subtree). Are you suggesting that "@thin" and "@@thin" should be treated the same way in this context? This is fine, but then isAnyAtFileNode() would need to be dumped and something else would have to be used. Does leo have another function in its API that complements isAnyAtFileNode() and catches escaped external file directives as well? > Changing this to @thin lets fcol work for all its > children, but the algorithm that calculates fcol must be forgetting to > check the current node as it has an offset of 9 rather than zero for > @thin's body text. I failed to reproduce this. An unit test that reproduces this problem would be good to have. I never noticed this behavior, nor when I implemented fcol back ago, neither now, when I played a bit inside quickstart.leo to reproduce the problem you've described. I wonder if it has something to do with caching (see the implementation of p.textOffset()) > Further thinking about fcol, I realize that it should have no meaning > outside of a external file generating subtree, and should either not > be shown in the status area then, or starred out. I might try to do this, but only when I'll get enough comments on things I've said above. I think it is possible to initialize p.txtOffset to None instead of 0, and if a None value is returned, it will be clear that an external file root was never reached, so the "fcol" part doesn't need to be shown in the status line at all. Of course, if we decide that any changes have to be made here, we should wait for Edward to cancel the commit moratorium first. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: @auto parsing error on dedented triple quote string
On Nov 1, 4:48 pm, Kent Tenney wrote: > BTW, I had to > [home/.leo/db] $ rm -rf * > > to see the change. I think it is a good idea to do this every time when pulling from trunk. Having a little shell wrapper that syncs the local branch and does the cleanup instead of issuing "bzr pull" directly serves me well. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: New output in console window
On Oct 29, 6:21 pm, Terry Brown wrote: > zpcspm wrote: > > skipping tag select3: c does not exists or does not have a frame. > > I think this happens when callbacks are made for a plugin that tries to > operate on an outline which has been closed. I would guess this only starts > happening after you've closed at least one outline. > > Have you enabled any new plugins recently? This is easy to check. $ stat ~/.leo/myLeoSettings.leo ... Modify: 2010-10-09 It's been 20 days since last change, I'm sure the reported output appeared very recently. As `git blame` shows, last change to myLeoSettings was related to `put_expansion_bits_in_leo_files` setting (remember my whining about expanded node records polluting diffs and Edward coming shortly after with an improvement), so even that change is not related to plugins at all. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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.
New output in console window
I always launch leo from console and sometimes look there (not always). Today I noticed some strange output that I didn't see before: --- skipping tag select2: c does not exists or does not have a frame. skipping tag select3: c does not exists or does not have a frame. skipping tag select3: c does not exists or does not have a frame. skipping tag select2: c does not exists or does not have a frame. skipping tag select3: c does not exists or does not have a frame. skipping tag select3: c does not exists or does not have a frame. --- I believe it's pretty recent, not older than a couple of days. I didn't notice anything that would break my usual workflows (so this is not a bug report), just dropping the console log here. I'm using current trunk (r3590) on linux. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Any patches re bug 613153: unable to describe root directory on thumb drive?
Wouldn't it be technically correct to use os.sep instead of hardcoded slash/double backslash constants? -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: split lower screen possible?
On Oct 23, 12:58 am, Graham Chiu wrote: > Cool .. yes that's it! Great. I'm pretty sure I complained a long time ago about not having a setting for controlling the splitting direction (horizontal on vertical) when doing `add-editor`. Splitting the body pane vertically looks good for the default setup, but with @string initial_split_orientation = horizontal, splitting the body pane horizontally as well could be more handy in certain scenarios. Now add- editor always splits the body pane vertically. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: myLeoSettings
On Oct 22, 11:51 pm, Graham Chiu wrote: > Hi > > Is there a minimalist myLeoSettings.leo file anywhere that I can download? You can build your own one easily. Here is my workflow: - open an empty outline - create a @settings node - paste the @enabled-plugins node from leoSettings.leo as child of @settings node - make sure that you add all your user-specific properties as children of @settings node - save it as myLeoSettings.leo, put in ~/.leo (for Linux) > I did get the stickynotes plugin working that way, but couldn't do the same > with the @string initial_split_orientation = horizontal directive Please see above. I suspect that your @string property node is not inside the @settings subtree. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: split lower screen possible?
On Oct 22, 7:56 am, Graham Chiu wrote: > vertical split lower screen? Do you happen to mean the "body panel" by "lower screen"? If so, do you aim for such a setup (see the screenshot below)? http://i.imgur.com/3oKQG.png If that's what you need, you could simply use the `add-editor` command -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: leo ftp
On Oct 17, 11:51 pm, Ivanov Dmitriy wrote: > There is one enhancement, that I don't know how to do myself: I don't > what to upload the files, that weren't changed since the last upload, > so I need some kind of DB table, that will have this structure: > > | local file name | server file name | last modify date time | > > If last modify has changed, then upload. Now I have this simple DB as > a matrix in code - files array. What is the best way to implement this > feature in python inside leo? I don't think, that Mysql or Oracle > would be good choice for this. :))) Are you sure you need a relational database? Don't mix databases with persistence, because that's what you need. I would use a database only if I would have a couple of tables, a couple of relations and using SQL would make it much easier. In your case, I would just use a dictionary with file names as keys and would store it using JSON. Recent versions of Python bundle JSON parsing modules by default and converting between JSON and simple Python data structures like list/dictionaries is the easiest possible thing. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Possible bug in @shadow logic
On Oct 9, 5:12 pm, "Edward K. Ream" wrote: > Please file a formal bug report. https://bugs.launchpad.net/leo-editor/+bug/657374 I simplified the workflow again, so it should be even easier to reproduce it. I added a reference link to this thread, but I believe the bug report at launchpad is self-sufficient. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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.
Possible bug in @shadow logic
Here is the simplest workflow I could get to reproduce the problem. A .leo file and a source code file (python) in version control (fossil). The source code file is linked into the outline as @shadow file. I add a class with a method (named method1()) to the .py file. Save and commit. Let it be r1. I add another method (named method2()) to the class. Save and commit (but commit to a new branch, to trigger a fork). Let it be r2. I update the workspace back to r1. Actually, I realize that method2() will call yet another method (method3()), so I revert back to r1 to implement method3() first, commit it to the trunk, then go back to the partially implemented method2(), complete it, commit then merge with trunk (which already has method3()). This is only the reason for switching to r1 that is not related to the @shadow issue. After updating the workspace to r1, I restart leo. The outline has a method2() node with empty body. Why? It shouldn't be there! After r1 there was nothing related to method2() in the workspace. If I close leo, delete the .leo_shadow directory and restart leo, everything is well. There is no method2() node in the outline anymore. So the @shadow cache somehow has higher priority than the actual files, which I think is not correct. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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.
Is persistence of expanded nodes really so important?
I'm failing to understand why. Here is my story. I have a small project in version control. I also keep the outline in version control. I think this is good, the outline serves as skeleton for the project, it evolves together with the project. I learned to ignore the diffs related to the header of the outline - I just don't look at them. I think I already saw on this list other people complaining about it too, I just don't remember the exact context to add a reference link to another thread. But the implications go further. I'm using branching often to emulate bzr shelve / git stash for putting away some unfinished changes when I'm in the middle of something. When I'm merging later, the outline file always produces conflicts. The header that stores data about the expanded nodes is different and I have to merge raw XML manually, which is not pleasant. I can think of a couple of reasons why leo itself is not affected by this. leo uses those reference files (which I personally consider a hack that tries to rather dodge the vcs implications than mitigate them). Also, leo development is mostly linear, not branched, so conflicts don't happen often. I will be extremely happy if one day that data goes away from the outline header. I don't see anymore how the persistence of expanded nodes has a major positive impact. When closing an outline, it is good to have a "resume entry point" for the next time, but this is achieved easily by cloning the node in question into the root, so it stays visible. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Can leo auto-reload an outline that was changed externally?
On Oct 1, 4:57 pm, "Edward K. Ream" wrote: > Leo's load-at-file-nodes will update all the @file, @auto, etc nodes > in the selected outline. Wouldn't that work? > > Edward What about the outline itself? Consider the following workflow: - I commit r1, the .leo file is in version control too - I add a new @thin node, the .leo file is changed - I commit r2 - I update the workspace to r1 - ??? - is it possible to have here the outline updated to its previous state (no new @thin node yet) without having to close leo, start leo again, then open the .leo file? -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Can leo auto-reload an outline that was changed externally?
On Oct 1, 2:35 pm, "Edward K. Ream" wrote: > Using a common .leo files should be easy enough: just put > everything that could change in an @thin node. I was hoping for a lazy automated solution. Putting changing parts into @thin nodes is a good idea, but adding a new source file (as one more @thin node) still changes the outline. I've noticed that if I modify an outline externally, leo warns me about changed content when I'm trying to save it, but that's a different story. I was hoping I could do "vcs_app update revision_id" in a terminal, then switch to leo window and leo would reload the changed @thin nodes or the whole outline if needed. Maybe there's at least some leo API function which I could stick into a button and explicitly force a full reload of the current outline (without having to close and reopen leo) every time I update the workspace to another revision? Another way would probably be to use @shadow, because I remember leo being able to detect external changes for them and refresh the tree. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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.
Can leo auto-reload an outline that was changed externally?
Is this possible? Restarting leo manually every time looks highly inconvenient, I'd like an automated approach. I need this for a scenario where I have a leo outline and a couple of external files in version control and I need to switch between revisions (this will trigger changes in both the outline and the external files). -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: can't open in external editor
On Oct 1, 3:02 am, Matt Wilkie wrote: > Where is the external editor setting kept? LEO_EDITOR environment variable works for me (Linux). See guessExternalEditor() in leoGlobals.py -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: installing leo on Ubuntu
I recall Ville posting on this list about his ubuntu ppa which contains leo. He will have to drop a comment here, since I'm not using ubuntu, and I never tried it. Here is the relevant thread: http://groups.google.com/group/leo-editor/browse_thread/thread/f72aa1583f7456d8/8cbc41f13b7c24c8 -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Emacs org mode at floss weekly podcast
On Sep 25, 12:20 pm, "Ville M. Vainio" wrote: > FLOSS weekly has an episode on emacs "org" mode (outliner mode similar to > Leo): > > http://twit.tv/floss136 > > I have tried org mode in the past, but it never stuck like Leo did > (partially because I try to keep my emacs use at minimum these days). > Nevertheless, the podcast is probably of interest to Leo users because > it deals with similar use cases. > > -- > Ville M. Vainio @@ Forum Nokia vim also has an interesting plugin called VOoM (http://vim- voom.webs.com/) It even claims to have some features inspired by leo :-) It is a good option for computers without X, where leo doesn't work. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: There is any way to enable multitab qt interface from myLeoSettings.leo ?
I'm not familiar with Kupfer and after a quick glance over its homepage I'm not sure I understand what exactly it does. Perhaps because my CLI experience biases me. If your goal is to avoid running an app with a command line argument, you can wrap the whole call into a shell script like this: --- #!/bin/bash launchLeo.py --gui=qttabs "$@" --- Call it for example tableo, put it in your PATH and make sure it actually can run leo (by using an absolute path to your launch script for example). -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: There is any way to enable multitab qt interface from myLeoSettings.leo ?
On Sep 24, 8:05 pm, Offray Vladimir Luna Cárdenas wrote: > Hi all, > > The more I use Leo, the more I need it open with my last leo files for > different subjects. There is any way to enable multitab qt interface > from myLeoSettings.leo ? > > Cheers, > > Offray It's a command-line argument IIRC. Like this: launchLeo.py --gui=qttabs -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Macroes in leo
If your LaTeX file is contained in a single leo node, you could set up emacs as external editor via LEO_EDITOR environment variable, launch emacs and do the macros thing. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Enhancing leo_to_rtf.py
A possible workflow would be: - register at launchpad (if you are already registered, skip this step) - learn the basics of bzr - create your own branch of leo - hack hack hack - when you're ready, make sure your changes didn't break any leo unit tests (since you'll be modifying a plugin, chances to break leo will be really low) - propose your branch for merging into the trunk -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: qt font size
On Sep 11, 7:48 am, tfer wrote: > To change settings, you must change the appropriate entry in the > stylesheet in: > > qtGui plugin-->@data qt-gui-plugin-style-sheet This recipe is functional for me on Linux with the current trunk. According to the gnx of the node, it landed into myLeoSettings.leo about 6 months ago and I don't remember it breaking. I'm using a custom combination of font-family and font-size for qt widgets and it works for me. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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.
Traceback related to todo.py plugin
This is what I see in the log pane: hook failed: close-frame, >, leo.plugins.todo Traceback (most recent call last): File "/home/shadow/leo/leo-current/leo/core/leoPlugins.py", line 325, in callTagHandler result = handler(tag,keywords) File "/home/shadow/leo/leo-current/leo/plugins/todo.py", line 391, in close g.unregisterHandler(i[0], i[1]) I pulled today and I'm almost sure I see this for the first time, so it must be pretty recent. This is an outline I'm using often although not on a daily basis. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: A "little" Aha re unit testing
On Sep 8, 5:23 pm, "Edward K. Ream" wrote: > 2. (Important) It is much easier to generate comprehensive unit tests > for small methods that do only one (simple) thing. Actually, this is the definition of an unit test - it tests a very small, atomic and independent piece of code and it completes very quickly (so you can have tons of them) :-). This peculiarity of unit tests is emphasized very well in the book "Working Effectively with Legacy Code" by Michael Feathers. While we can learn a lot from others, discovering such little "truths" ourselves makes us excited indeed. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Bug: not opening leo file when there are non-english characters in the path
On Sep 7, 7:48 pm, "Edward K. Ream" wrote: > Thanks for this. It may be helpful. What version of Python are you using? I'm on Python 2.6 as the traceback shows (see the /usr/lib/python2.6 path). I could trigger the traceback using r3339 of trunk. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Bug: not opening leo file when there are non-english characters in the path
A wide guess is that some path is not converted properly to unicode. I'm not using Windows, but I'm running Linux with a non-utf Russian locale (koi8-r) and I can trigger similar problems on purpose. My test directory is /tmp/тест If I run leo in that directory (I don't even open and outline, just launch leo), I see the following in console: /home/shadow/leo/leo-current/leo/core/leoGlobals.py:244: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal if theDir not in sys.path: and a more detailed traceback in the log pane when leo starts: Traceback (most recent call last): File "/home/shadow/leo/leo-current/leo/core/leoPlugins.py", line 248, in callTagHandler result = handler(tag,keywords) File "/home/shadow/leo/leo-current/leo/plugins/plugins_menu.py", line 200, in createPluginsMenu plugins = [PlugIn(m, c) for m in modules] File "/home/shadow/leo/leo-current/leo/plugins/plugins_menu.py", line 310, in __init__ self.filename = g.os_path_abspath(filename) File "/home/shadow/leo/leo-current/leo/core/leoGlobals.py", line 3353, in os_path_abspath path = os.path.abspath(path) File "/usr/lib/python2.6/posixpath.py", line 338, in abspath path = join(os.getcwd(), path) File "/usr/lib/python2.6/posixpath.py", line 70, in join path += '/' + b UnicodeDecodeError: 'ascii' codec can't decode byte 0xd4 in position 5: ordinal not in range(128) Edward, I'm providing this in hope that it might help you to locate the problem in the code faster. If this confuses you, feel free to ignore it (after all, my scenario is a bit different and it might trigger the problem in other part of the code). Personally I'm not and will never be affected by this, because I always try to use English file/directory names. There's a slight chance that this might affect other Linux users, because most Linux distros nowadays use utf locales by default. But for non-English Windows users this is indeed a problem. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Is it time to retire tk?
On Aug 30, 6:05 pm, Terry Brown wrote: > I think the issue is, do you expect the functionality of Tk to stay > at its present level or to decline over time? It is also possible that in the future somebody would need a new leo feature backported to tk for personal use. This is why I thought having a distinct branch in the first place. After the fork happens, current trunk will always contain a tk functionality that is declining over time, because ideally nothing tk related will be done there. The other branch could get more commits over time, if a tk related bug will be fixed or a feature from the trunk will be backported. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Chapter 7 of docs seems to contain some wrong statements
I solved my variable highlight issue by using a workaround: I open the body in an external editor (gvim) and just use highlight there. Regarding the reported bug - I filled a bug report: https://bugs.launchpad.net/leo-editor/+bug/626835 -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Is it time to retire tk?
I would suggest to use the term "deprecate" instead of "retire" or "remove". This is how I see it. If the next stable version will be the last one supporting tk - release it, then create a branch right after the official release and leave it unchanged. This way people in need could still use that branch in its current state (after all, a lot of effort was put into tk, no need to forget it completely). An exact branch copy will become the current trunk instead and will have everything tk related removed from it and eventually the leo core simplified if the removal of tk would make that possible. It's good Edward brought this issue up, because we had it coming anyway. Even if qt GUI was strongly advocated, it was never done at the expense of hurting the tk GUI, so the fact that the qt GUI is used almost exclusively (at least judging by the content of this group) is something natural. Putting tk aside in a reasonable way makes sense, this will spare both developers and bug reporters from thinking about compatibility with tk when implementing new features / writing GUI related bug reports. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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.
Chapter 7 of docs seems to contain some wrong statements
I was studying Chapter 7, particularly section "Getting and setting
body text directly" looking for some documentation hints.
The following mini-scripts don't seem to have any effects on my setup
(linux, python 2.6, pyqt 4.7, current trunk of leo with qt GUI):
w = c.frame.body.bodyCtrl
w.setBackgroundColor('red')
w = c.frame.body.bodyCtrl
w.setBackgroundColor('#FF')
w = c.frame.body.bodyCtrl
w.setForegroundColor('red')
w = c.frame.body.bodyCtrl
w.setForegroundColor('#FF')
These seem to work in the tk GUI, but not perfectly. There seems to
happen some interference between them and the colorer, because not all
the body text is affected.
How I found this. I was looking for a way of writing a script button
that I could press after selecting a piece of text
(w.getSelectedText() seems to return it correctly) in the current body
and have all occurrences of it displayed with a certain foreground/
background combination (I couldn't find any hints in the docs so I'll
be grateful if somebody teaches me how to do it). I need this
functionality because I think it could help me study unknown python
code (big legacy methods). I plan to emphasize variable names this way
to get a general view on their references inside a function.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to leo-edi...@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: Trivial leo script doesn't work
On Aug 23, 5:13 pm, "Edward K. Ream" wrote: > You need to copy positions if you save them in a list. If you don't, > they will move, eventually becoming 'None'. Could you please elaborate a bit on this? No need to go very deep, just the general principle, because I'm missing it. The funny thing is that I know positions may become invalid if the outline changes. By "outline changes" I use to understand situations like "a different node gets focus", "a node gets deleted/added/moved". This is perfectly in accordance with leo docs - specifically, section "Ensuring that positions are valid" of "Chapter 7: Scripting Leo with Python" - I've read that for the first time long time ago, in the pre- sphinx era, when I was still using leo with the tk GUI. But I see "outline changes" and "saving positions into a list" as very different things, that's why I didn't even bother to try the copy trick in the first place, but whined here :) Do you see any mistakes or missing pieces in my logic? -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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.
Trivial leo script doesn't work
Copy the following snippet, save it as leo outline, open the file with leo --- cut here --- test @button script sorted 1 3 2 for p in c.all_positions(): if p.headString() == 'sorted': children = list(p.children()) headlines = [x.headString() for x in children] print headlines break --- cut here --- For redundancy I pasted the same xml snippet here: http://pastebin.ca/1923111 This is the error I see in the log pane: --- cut here --- exception executing script AttributeError: 'NoneType' object has no attribute 'headString' line 450: * line 451: return self.v.headString() line 452: line 453: def cleanHeadString (self): --- cut here --- I generally don't use leo to script leo itself, so I don't know a lot of "script leo the right way" and "don't do it this way" tricks. I occasionally write small scripts to spare myself from doing monotonous manual management of nodes in an outline. When this thread is exhausted, I expect to have not only the attached script working, but also to learn about a new pitfall, to avoid it in the future. That's because I assume it's me doing something wrong by default, it's not leo's fault/eventual bug. I'm using the current trunk of leo (r3275) with python 2.6.4. on linux. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Using Bazaar to run latest development version instead of latest stable version [was: Re: nav_qt not working]
On Aug 19, 10:08 am, "taa, Leo Newbie" wrote: > Even though Chapter 1 > recommends installing a friendly GUI, the command line does seem > simpler. But Bazaar Explorer is much cooler. :D Of course you are free to use the approach that suits you best. But when you are making the first steps, it makes sense to use some trivial workflows that require minimal efforts. After you get used to it, of course you can experiment more and look for alternate ways. I find it easier to use the command line when I need to branch/clone a repository and when I need to pull the latest updates. This is true for any source control tool, not only for bzr. Yet I prefer a GUI frontend (if it is available) to see the latest changes, because it speeds up the process. After pulling the changes, I do 'bzr qlog', which launces the GUI. Double clicking on a revision shows me the changes in that revision. With pygments installed, I even get source code highlight. Of course I don't see a problem to achieve the same using 'bzr log | ', find a revision, then do 'bzr diff' and redirect the output to vim (which can do highlight), but that's just more to type. > getting the snapshots from > http://www.greygreen.org/leo, seems even simpler as it doesn't involve > installing Bazaar at all Running leo from the snapshot has the advantage that it's indeed easier - you just need to download the tarball and unpack it. But if you bump into a problem that was introduced recently, you'll have to deal with the repo anyway, because you would want to do bisection (manual or automatic, if your source control of choice supports it) and find the exact revision number. So snapshots vs bzr is not a clear win, it's a tradeoff > It's also quicker to download -- 7MB > zipped, 24MB unzipped, vs. 73MB-76MB using bzr/Bazaar Explorer. This is ok, because the bzr repo contains all revisions, all history. Anyway, you have to download this big amount only once, because a further 'bzr pull' will download only the missing newest changes (if there are any). -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Using Bazaar to run latest development version instead of latest stable version [was: Re: nav_qt not working]
After installing bzr, can you access the command line version of it? That's really all you need to get the sources and periodically sync them. I have a strong feeling that you went the wrong way by trying to use a GUI frontend (this is totally IMHO, because you are following the leo docs). If you type 'bzr' in a command prompt and get output similar to this: Bazaar -- a free distributed version-control tool http://bazaar-vcs.org/ Basic commands: bzr init makes this directory a versioned branch bzr branch make a copy of another branch bzr addmake files or directories versioned bzr ignore ignore a file or pattern bzr mv move or rename a versioned file bzr status summarize changes in working copy bzr diff show detailed diffs bzr merge pull in changes from another branch bzr commit save some or all changes bzr send send changes via email bzr logshow history of changes bzr check validate storage bzr help init more help on e.g. init command bzr help commands list all commands bzr help topicslist all help topics it means that you can use it. If you go to https://code.launchpad.net/leo-editor, you'll see a hint there about getting the source code: bzr branch lp:leo-editor Before doing this, navigate to a proper directory where you want to keep the leo repository. After the command finishes, you will have a leo-editor directory. cd into it. For further updates, do a 'bzr pull' while being in this directory. If you do it immediately, no more changes will be retrieved, because you've got a fresh copy when branching. Doing this on a daily basis will retrieve only the latest changes from launchpad. You have a python script called launchLeo.py - this is the leo launcher. I don't know why is leo/core/leo.py mentioned in the docs, perhaps it's obsolete and should be fixed, but my repo doesn't have such a file. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: nav_qt not working
On Aug 15, 9:53 am, "taa, Leo Newbie" wrote: > It looks like I need to install the latest Leo rev to fix? Dealing with the latest development version is generally a common requirement if you want to complain about a bug, because often issues spotted in the stable version are already fixed in current trunk when some people bump into them for the first time. I encourage you to start using the bzr trunk instead of the stable version. It generally stays stable and you can mitigate any risk of eventual data loss if a bug slips in during changes by having both outline files and external files in source control. If you can use this workflow and pull the leo source daily, you will also do a favor to the whole community, because you will be among those who spot problems as soon as they are introduced into the trunk. Such situations usually have the highest priority and are being dealt with immediately. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Leo 4.7.1 Windows installation problem: PyQt not installed, reverting to Tk UI
On Aug 13, 1:20 pm, Norbert wrote: > The same problem occurs with Python 2.7 too. I think it is wrong to make the statement to look in a way that could be treated as "it's a python problem" or "it's a pyqt problem", this is misleading. I think it would be fair to say it's a problem of the pyqt installer for Windows or it's a problem of Windows itself. I think I do have the right to make such a claim, and I can assure you it contains no hidden rants against Windows. I've come a long way, in the past I had to manually build packages for qt4 and pyqt4 from source, because I've started to use leo before my Linux distribution of choice started to package officially qt4 and pyqt4. I NEVER experienced nightmares like those I regularly read on this group and other resources. My concern has a reason. I wouldn't want leo newbies to see these threads and consider that malfunctions are leo's fault, python's fault, or pyqt's fault, while they seem to be specific to a particular setup, involving only a certain operating system. I also have another reason, which is more selfish: I don't scream around that leo is so cool and everyone shall use it, I have a strong posture against such advocating/preaching, but I never miss a chance to tell people about leo when I see that they do something which could be done better using leo and I know how easy sometimes users project the malfunctions of a certain app to the person that suggested it to them :-) I'm not going to advocate you to change your operating system if you use Windows. All I want to say is that if you have no strong reasons against trying a mainstream Linux distribution, you certainly shall give it a try. It's much more suited for hacking (learning/using/ improving leo is certainly true hacking, in the good sense). -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Leo 4.7.1 Windows installation problem: PyQt not installed, reverting to Tk UI
On Aug 12, 11:59 pm, Steve Allen wrote: > it defaulted to Tk unless I used the "--gui=qt" flag AFAIK, leo from current bzr trunk tries to use the Qt GUI by default. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Find problem
On Aug 9, 1:37 am, robertc wrote: > Not getting answered, so I'm asking again: > > Is this is a known issue with Qt UI ? that hitting "Enter" after > entering search term in Find - nothing happens. > Just want to make sure this is a problem so I can give up on it and > use "ctrl + f" > > thanks > Robert I wonder if you didn't get an answer because nobody is using the Find tab anymore nowadays? Personally I use the Nav tab instead. To be able to use it, you have to enable the quicksearch plugin. The screencast that Ville recently made covers using it and the plugin file quicksearch.py has an user- friendly help in the docstring. Ideally, I wouldn't mind if the Find tab becomes obsolete, gets hidden (unless it contains some additional functionality that I'm not aware of and that is used by some people) and the Nav tab gets renamed to Find. Another thing to remember if this will ever be considered is that some people may still use the tk GUI, which is not officially completely dead, so it would be nice if somebody could port (or extend) quicksearch to tk. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: First Leo screencast at youtube
On Aug 8, 8:17 pm, "Ville M. Vainio" wrote: > Unfortunately youtube lowers the quality quite a bit (at least with my > settings). The negative impact is minimal, opening the external file in vim was the worst part, due to black background perhaps. But that was just a couple of seconds. > Again, this is mostly useful for newcomers. Doesn't mean it shall be ignored by those who don't consider themselves newcomers anymore. I learned something new from it: I didn't know I could mark multiple nodes then clone all of them in a single step, this is certainly neat. Thank you for the good work. If you plan to do more of these, I have a suggestion. Please show some less common usage tricks which you consider valuable (due to time saving or for other reasons). I believe this will have a high appeal. A duration of 5-7 minutes is ideal - the screencast contains a decent amount of informational load, yet it ends before starting to become boring :-) -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Feature suggestion
On Aug 6, 4:28 pm, Kent Tenney wrote: > On Mon, Aug 2, 2010 at 7:37 AM, Edward K. Ream wrote: > > > On Sun, Aug 1, 2010 at 12:58 PM, Kent Tenney wrote: > > >> Navigation history seems like an aspect of undo / redo, appropriate for > >> core. > >> I think it would be useful if Leo kept a list of nodes visited, > >> possibly several lists: > > >> - nodes having received headline focus > >> - nodes having received body focus > >> - nodes having been edited > > > I have much more important projects on the list now, as I'll soon explain. > > Since this is my itch, I'd best scratch it. > > I want a file on disk which is Leo history, a record of nodes visited, whether > the body received focus, and whether the body content changed. > I guess it is the equivalent of a database 'journal' file. > > (stuff like a diff for the changes might be somewhere down this road) > > It seems that if I hook 'receiveFocus' and 'loseFocus', it should be pretty > straightforward. > > Any guidance appreciated; > - correct method calls ... > - should be written as a plugin? > - already solved somewhere? > ... > > Thanks, > Kent I would use nav_qt.py plugin for reference, it seems to do something similar. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: Is something basic missing from Leo?
On Aug 6, 9:50 am, taa wrote: > Suggestion #7: Change 'Portable' to be 'Cross platform'. When I first > saw the word 'Portable' I thought that meant I'd be able to run it on > a flash drive. I think this is true as well, assuming leo can find its dependencies (python and pyqt/tkinter at least). Being a python app, leo doesn't need to be installed. You can run it via launchLeo.py as soon as you get a copy of the source code repo using bzr. I've been doing this for a long time and I don't remember it to fail. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: leo import issue
On Jul 29, 7:21 pm, "Edward K. Ream" wrote: > Please create a wish-list bug for this. There almost certainly will > be some complications, but we must start somewhere. Done https://bugs.launchpad.net/leo-editor/+bug/611413 I made the bug report extremely laconic and neutral, feel free to improve the content. The discussion in this thread happened some time ago, yet I remember that there was another thread aiming at the same issue. I added references to both threads in the bug report, so the ideas that appeared there wouldn't get lost. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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: @shadow node converted to @edit node
On Jul 17, 6:25 pm, thyrsus wrote: > Please report your further experiences; I've got a lot of @shadow > nodes. I take it this isn't happening for all @shadow; I've got a lot > of them, but this hasn't happened for me. Can you speculate on what > may have triggered this? Nearly all my @shadow nodes began as an > import to @file, which I then converted to @shadow. > > - Stephen I didn't notice more than I've reported. I've tried to follow the workflow I've asked about myself in the initial post (Would renaming the @edit note to @shadow and refreshing from disk suffice?) but I was still getting a single flat node containing the whole file body. Finally I just deleted the node, used "file -> import -> import to @file" again, then renamed the node to @shadow. This worked. I wouldn't want to try reproducing my issue because looking for some wrong behavior makes me more subjective a priori. Assuming that this is a bug, it will eventually pop up again. I'm prepared to see this, so I will be paying more attention to details if it happens again. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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.
@shadow node converted to @edit node
I just opened a leo outline that contains a @shadow node and it added the external file as @edit node instead. I'm running current trunk and the outline was edited last time before new-sentinels was merged into the trunk. What is the correct workflow in this situation? Would renaming the @edit note to @shadow and refreshing from disk suffice? -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@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.
