Re: open with feature - next steps

the default setting from LeoSettings.leo, ensure that you have specified the path yourself). subprocess should work similarly b/w linux windows. Does the edit from rclick menu work for you? It uses the same method of launching... -- Ville M. Vainio http://tinyurl.com/vainio

Re: rST export from leo 4.6.2

needed statement should be removed. The functionality is available, it's just moved to core now (so you always have it). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Updated pdf docs available

for a little project, he could work on replacing all the gif files in bzr with png files. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post

Re: open with feature - next steps

w/o one. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: open with feature - next steps

the weird hardcoded windows path from vim.py and just use gvim.exe. Then, vim.py will work w/o manual configuration as long as it's on path. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed

Re: open with feature - next steps

. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: Open Users Guide menu item still doesn't work

in user guide, we would have this for free (just run sphinx). Something for 4.7, I think. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post

Re: Updated pdf docs available

.  Where does it show up? E.g. go to page 21. In the heading, it says Chapter five. The actual title for the chapter is Chapter 2: Tutorial introduction to leo. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you

Re: Updated pdf docs available

to the old files everywhere. Try using bzr bundle to provide the patch. Of course it's too late for rc1, but perhaps for the final :-) -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed

Re: Open Users Guide menu item still doesn't work

version should still be there. I removed it, and it shouldn't be there. It was only for the pre-sphinx html manual. The issue was not that it was not up-to-date - rather, it was up to date, and caused the files to appear in bzr diffs every time you generated the docs. -- Ville M. Vainio http

Re: *critical bug* - Leo 4.6b1 destroying data

is that if you use @file nodes, you set yourself up for data loss. @file nodes are deprecated, and @thin nodes should be used instead. I complained about the same issue earlier myself. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message

Re: *critical bug* - Leo 4.6b1 destroying data

with @thin in headlines and save, and it will work. With the side benefit of not losing your data occasionally ;-). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group

Re: contextmenu: the new edit in external editor approach

On Sat, Jul 4, 2009 at 3:47 AM, TLt...@tltools.net wrote: Any chance documentation on the new contextmenu.py plugin can be added to the Users Guide before the rc1? It's in trunk now. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You

Re: *critical bug* - Leo 4.6b1 destroying data

test would have caught such an horrendous problem, but apparently not. That being said, @file nodes are prone to similar errors when the files get out of synch as well. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message

Re: *bug* - PHP syntax colouring

speed right now, and anything that compromises performance is a bad idea at this point (unless it only slows down php ;-). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: *bug* - PHP syntax colouring

... @language inphp ?php @others ? @language php more html... Though I really think the simplest solution is adding html support to php mode at all times. That way there would not be a need to be too clever at all. -- Ville M. Vainio http://tinyurl.com/vainio

Re: Vim mode users: your top 3 complaints, please

On Sat, Jul 4, 2009 at 6:49 PM, Edward K. Reamedream...@gmail.com wrote: I'm surprised at the deafening silence.  Are there really no urgent fixes needed to support vim-like operation in Leo? Well, we have a good vim-the-real-thing support in place already, so... ;-) -- Ville M. Vainio http

Re: Coming in Leo 4.7: all clones are the same node

, or len(parentlist) 1. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: Coming in Leo 4.7: all clones are the same node

for bookkeeping. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: Coming in Leo 4.7: all clones are the same node

. Here is the list of attributes in position: http://pastebin.com/f3f8880c1 I think you'll agree that almost all of them (not the iterators) pertain to nodes, not positions. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message

Re: Coming in Leo 4.7: all clones are the same node

know the places where that structure is to be updated (position connect/disconnect to tree). And, we already have equivalent structure (tnodesdict). It's needed to detect clones in @thin node reading. -- Ville M. Vainio http://tinyurl.com/vainio

Re: Coming in Leo 4.7: all clones are the same node

. they are operations that apply equally well to any cloned version). Just to illustrate the issue, some examples: p. at* is* set* clear* copy* .h .b -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed

Re: Coming in Leo 4.7: all clones are the same node

staying with DAG, so listing descendants is a trivial operation... We already talked about the general graph route and it won't work, such functionality is best reserved for backlinks.py and the likes. -- Ville M. Vainio http://tinyurl.com/vainio

Re: beta 2 data loss

on save. Was some of the data cloned from a @thin file? One cause could also be that you had the same .leo document open twice, and saving a wrong one overwrote your previous changes. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received

Re: Starting Leo with TCL ui?

it start tk automatically if qt startup fails? -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: beta 2 data loss

) being disabled. Where are the logs I should post? They appear on console when you starting leo. So now they are probably gone :-(. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed

Re: Default workbook.leo always remain opened

. I don't think it should become the default behaviour though, at least I like my workbook.leo open at all times -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor

Re: Default workbook.leo always remain opened

workbook.leo, even. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: Default workbook.leo always remain opened

- but personally, I think workbook.leo is 100 times more useful. You can start jotting notes on that immediately when starting leo, whereas starting a new leo document, is, well... how often do you start new documents anyway? -- Ville M. Vainio http://tinyurl.com/vainio

Should @plugin work?

I added @plugin tomboy_import.py to my workbook.leo and restarted leo. However, the plugin is not loaded. am I doing something wrong? -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed

Re: Default workbook.leo always remain opened

;-) -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: Default workbook.leo always remain opened

be an interesting Qt finger exercise for someone Including friendly Last modified: 2 hours ago field, and other nice stuff. It would be pretty cool. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you

Re: Nodes in a db?

?) just has to turn it into an easily usable product. This is not eminently practical for development teams (putting zillions of files in vcs, one file /node), but handy for solo developers. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You

Re: open with feature - next steps

a hitch anyway. Though I clearly see why it doesn't work now, it needs to be fixed at c.openWith level. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group

Re: open with feature - next steps

what area needs to be tweaked if it still fails. Not having windows setup in place, I can't test these exhaustively myself. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: Coming in Leo 4.7: all clones are the same node

descendant nodes (clones?) as a handy unidirectional one-to-many relationship. BTW, softlinks.py might benefit from rclick submenu (follow = mynode). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed

Re: open with feature - next steps

ideas? Nope. With qt, the plugin is diabled and the moving is done by contextmenu.py. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post

Re: The status of the one-node branch: a conjecture

? I can't think of a sensible thing the traversal could do... -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo

Re: The status of the one-node branch: a conjecture

of all A's descendants. Wouldn't just removing A from B's parents list suffice? That makes sense, since A is no longer a parent of B. This is practically a free operation. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message

Re: The status of the one-node branch: a conjecture

is so cheap that it's practically free, and in that case your practical problem with pathological tree depth is presenting such a tree in tree widget anyway (unless you are hoisting like mad). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You

Re: Coming in Leo 4.7: all clones are the same node

could be applied to either Do you care about cloned siblings? If not, you can store your data to parent uA, accompanied by the gnx of the child. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed

Re: Rev 2210 problems/questions

stuff. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: Default workbook.leo always remain opened

editors project, since it's just about fiddling with what widget is a child of what widget, done at the widget creation time. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: B3 on Friday, July 10

hashlib' (you, that's my hashcaching code). The old md5 module is deprecated on 2.6. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group

Re: open with feature - next steps

/qmenu.html#popup You may need to shove the menu to a global var (or self.qtmenu, or something) to avoid it being garbage collected. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed

Re: open with feature - next steps

On Fri, Jul 10, 2009 at 2:44 PM, Ville M. Vainiovivai...@gmail.com wrote: Can you try something? At qtGui.py, line 5438. Try changing menu.exec_ to menu.popup. Bah, I meant line 6124. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You

Re: open with feature - next steps

) or whatever conditional code you meant by the statement:   Try calling it with shell=False if (and only if) data argument is tuple. This prevents the Vim program from launching. As requested by Edward, I'm only doing this after rc1. -- Ville M. Vainio http://tinyurl.com/vainio

Re: open with feature - next steps

before rc1. Right now, the workaround is not to use mod_tempfname.py. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email

Re: open with feature - next steps

h(c,p,menu) -a = menu.exec_(menuPos) +a = menu.popup(menuPos) +self._contextmenu = menu This works fine on Linux (but so did the old exec_) ;-) -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received

One more fix for rc1?

) and this seemed to fix it. It might be good to get this in for rc1 as well, because this is probably the behavior we want in the final - and it makes sense to give this as much testing as we can. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You

Re: One more fix for rc1?

On Fri, Jul 10, 2009 at 7:51 PM, Edward K. Reamedream...@gmail.com wrote: Sorry.  Too late.  However, the trunk is open, so feel free to push it. Ok, too bad. Pushed to trunk. I'll proceed with creating the .deb for 4.6 rc1. -- Ville M. Vainio http://tinyurl.com/vainio

Re: One more fix for rc1?

On Fri, Jul 10, 2009 at 8:31 PM, Ville M. Vainiovivai...@gmail.com wrote: I'll proceed with creating the .deb for 4.6 rc1. I noted you created tag 4-7-rc1. I guess you meant 4-6-rc1. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You

Re: Leo 4.6 rc1 released

-1_all.deb you might want to upload that to sourceforge as well. It should work with Jaunty, Karmic and debian (sid / lenny). It's vastly recommended over the source package, since it gives you: - 'leo' command - menu item - file association - icon -- Ville M. Vainio http://tinyurl.com/vainio

Re: Leo 4.6 rc1 released

/images/626.png http://imgbin.org/images/627.png (they won't be on imgbin forever, so don't link them) I do think qt ui screeshots will be a much better sell than the tk ones for prospective users. Yes, I cleverly staged todo.py icons for leodocs.leo ;-) -- Ville M. Vainio http://tinyurl.com

Re: qt panel arrangement

On Sat, Jul 11, 2009 at 9:24 AM, uve...@gmail.comuve...@gmail.com wrote: �...@strings[vertical,horizontal] initial_splitter_orientation = horizontal It's @string initial_split_orientation = horizontal That's all that is needed. -- Ville M. Vainio http://tinyurl.com/vainio

Re: Leo 4.6 rc1 released

LeoSettings.leo (and add the custom plugins you want afterwards). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo

Re: Leo 4.6 rc1 released

alteration. Is this fixed in RC1?  ( unable to download the RC1 from bzr ) No, such a feature is not implemented at all in qt ui. Probably won't be for the final either ;-). File a bug on launchpad about it to get it tracked properly. -- Ville M. Vainio http://tinyurl.com/vainio

Re: @path usage question

in contextmenu.py refresh from disk extra functionality. If I were you, I would do introduce @module tag (e.g.) os.path, and make an g.act_on_node handler for automating this (without polluting precious gui-visible @button namespace). Or use @g.command. -- Ville M. Vainio http://tinyurl.com/vainio

Re: @path usage question

and the buttons are stacked vertically. If anyone knows how that setting could be persisted, I'd like to know. I'm afraid that hasn't been coded yet. :-) -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you

Re: open with feature - next steps

the menu is popped up). Having multiple values in EDITOR would be bad, because it would break many other unix programs (e.g. bzr). We/someone might want to introduce a flexible way of adding the rclick items by just editing the outline, but we'll see what the best way would be. -- Ville M. Vainio http

Re: Leo 4.6 rc1 released

.  Anyone have any other suggestions? I guess it doesn't matter as long as they are linked from the home page. Screenshots are the first thing users look for when trying to find out whether a program is worth checking out... -- Ville M. Vainio http://tinyurl.com/vainio

Re: Leo 4.6 rc1 released

to extract some money (probably not much) out of leo development ;-). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email

pudb + leo debugging

to launch it: a = 1 b = 2 g.pdb() c = 3 Note that if you want to use the ipython mode, you should launch leo with --ipython (or you'll get mainloop errors). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you

Re: Qt vs. Tk gui

gui. Some plugins. The only way to know is to try out, since I don't think anyone's done a systematic tally of dark corners. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google

Re: open with feature - next steps

of correctly making the change that you proposed. Yes, I will do it. I actually have plans for a more flexible approach Alright, I got it working (but not pushed yet). Actually, the spaces in file names work in Linux as well (though such behaviour is generally frowned upon ;-). -- Ville M. Vainio http

Re: pudb + leo debugging

variables. Importantly, when you running leo with --ipython switch, g.pdb doesn't work at all (due to readline input hook). pudb, on the other hand, doesn't use readline. Therefore, pudb is currently the recommended way of using debugger with leo+ipython combo. -- Ville M. Vainio http://tinyurl.com

Stable branch trunk

will use with mercurial. If they find a bug in python 2.6.whatever, they fix it in that branch first, then merge from that branch to trunk (so python 2.7 will receive it). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message

Re: Stable branch trunk

, revert those files (e.g. from bzr qcommit checking gui) before checkin. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email

Re: Trouble in leo-4-6 branch: please hold commits to trunk

(and only select the files I really want to commit - usually .py files) - bzr push Then, to get my ~/leo-editor up to date again: cd ~/leo-editor bzr pull -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you

Re: Can't move nodes with mouse

position specific features. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: Can't move nodes with mouse

. For example, if the use case is easily creating clones, we could just make it easier to create clones (ctrl + drag - clone here). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: Running Leo + IPython

this, or if this was some known change in 4.6. I have updated the documentation, but it's not generated for the website yet. The way to launch ipython + leo (qt) is: python launchLeo.py --ipython then, press alt + i in leo (to associate ipython session with currently active controller) -- Ville M

Re: Can't move nodes with mouse

. Is it tkinter or PMW or whatever it's called we need? As said before, it's pmw that still is to be ported to py3k. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo

Re: Leo 4.6 final coming Friday. Please test

final branch works for this. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

rst project of interest

http://blog.enthought.com/?p=127 It may be that the codebase could be worth looking at. I find the prospect of doing a full sphinx rendering of a document in real time quite fascinating :-). -- Ville M. Vainio http://tinyurl.com/vainio

Re: rst project of interest

want to add this to leo as plugin: https://svn.enthought.com/svn/enthought/AppTools/trunk/enthought/rst/rest_editor_model.py sphinx_rest_to_html is the interesting function. Apparently, it can generate default sphinx document html without much environment setup. -- Ville M. Vainio http

Re: rst project of interest

. not on save or explicit tangle step). Conceivably, the easy and non-intrusive thing would be to use @auto-rst for this, and have an external process do the sphinx + show step every time the file is saved. -- Ville M. Vainio http://tinyurl.com/vainio

Re: Merge question

it manually than find the correct way to do it in bzr. The manual operation is roughly like: bzr diff -r STARTREV:ENDREV ~/mypatch.diff cd ~/target-branch patch -p0 ~/mypatch.diff or just do it by hand if you don't have 'patch' (e.g. by default on windows) -- Ville M. Vainio http

Re: rst project of interest

to the final output. I think the best implementation is a new process that monitors a file. That way, it's not really leo-specific, and it's easy to do. Leo just needs to tell it what file to monitor. -- Ville M. Vainio http://tinyurl.com/vainio

Re: Thoughts on Leo coding style

the section deals with in section description. If your section does a boring calculation on my_data and creates my_result, it could read: munge my_data to stringlist my_result Unless you mention that, the reader is going to be lost about where my_result came from. -- Ville M. Vainio http

Re: What's your favorite way to discover nifty new programming tools, ideas, etc.?

that stuff) -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

~/.leo/plugins

the distribution 'plugins' directory, because the users could then download the latest leo plugins from bzr without having to wait for new version of leo. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you

Re: ~/.leo/plugins

there and doing the initialization. The point 5 is probably the best short-term plan, since it gives us unlimited tweakability without resorting to rules in .leo files. It's also less of a security risk than autoexec kind of scripts in .leo files. -- Ville M. Vainio http://tinyurl.com/vainio

Re: wrong active window

On Fri, Jul 17, 2009 at 5:37 PM, uve...@gmail.comuve...@gmail.com wrote: PS: should I open a bug in launchpad? Yes. I wonder whether the recent lift() change did this... -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received

Re: Minor issue in settings' dox

support full unicode character set in the first place? -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: Minor issue in settings' dox

encoding glitch). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: Any good way to get build numbers?

between bzr and cvs. Every time you do a build, you could run bzr version-info and put the output in a file. E.g., for doing the bzr snapshots of the debs, I run the following ileo script: verinfo= !bzr version-info bzr_revno = verinfo.grep('revno').fields(1)[0] -- Ville M. Vainio http

Re: Minor issue in settings' dox

case is better served by users doing some kind of file format conversion with an external tool. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post

Psyco rebirth

Exciting news for Leo: http://mail.python.org/pipermail/python-list/2009-July/720291.html Leo has a few hot spots that we coud cherrypick for optimization. I'm thinking of external file import (when cache is not in place yet), syntax highlighter, and perhaps tree drawing. -- Ville M. Vainio

Re: The first dents in the new car: 4.6.1?

not be that bad an idea... -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: loadOnePlugin considered harmful for ui

(with no actual module loaded). This is quite worrisome. In general, we should prefer normal import as much as possible, and __import__ when we don't know the class name (e.g. when loading plugins). -- Ville M. Vainio http://tinyurl.com/vainio

Re: What's the best blog software?

On Tue, Jul 21, 2009 at 5:09 PM, Edward K. Reamedream...@gmail.com wrote: What do you all think about google blogs?  Is google the new evil empire? :-) Unfortunately blogger (the google blog product) is not quite up to the standards of other google products. Wordpress is better. -- Ville M

Howto: @buttons to change chapters

-- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

psyco test

increase is impressive enough in itself. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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

Re: psyco test

of the command line. I don't think we should do full psyco'ing anyway, to prevent memory bloat. Psyco is best applied in hand-picked code segments; perhaps we should enable/disable psyco with g.use_psyco (just like we do with unified nodes currently). -- Ville M. Vainio http://tinyurl.com/vainio

Re: Disabling coloring after x characters can be confusing

, not a bug. Why do you have such large nodes in your @auto tree? Perhaps there is a bug in @auto import? -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group

Re: Disabling coloring after x characters can be confusing

trickier to implement of course. That would suck IMO - then, you would have to pay the performance penalty anyway. It's much better to fail immediately. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you

Re: Disabling coloring after x characters can be confusing

is a good default. Why do you have such large nodes in your @auto tree? Perhaps there is a bug in @auto import? These were .h files.  Anyone who can parse them into pieces automatically is a better programmer than I. Fair enough ;-). -- Ville M. Vainio http://tinyurl.com/vainio

Re: newbie looking for clue

' pr_node.b = pingres ... and variations on the same scheme. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo

Re: beadList (nodehistory) update linearly degrading performance (positionExists )

think clicking around with node history navigation arrows is the only thing that should move the bead pointer left. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor

<    5   6   7   8   9   10   11   12   13   14   >