library, which would be impossible if Leo was under GPL. Let's
just let this issue rest move on...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group
the user what headline types the plugin adds act-on-node
support for).
--
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
On Mon, Feb 23, 2009 at 7:06 PM, Edward K. Ream edream...@gmail.com wrote:
Thanks for this. I hardly ever click in the outline pane these days, so I'm
not a very good tester.
Me neither, but it fixes the scrolling with cursor keys as well.
--
Ville M. Vainio
http://tinyurl.com/vainio
of options, but
double-click remains the obvious and fast-to-execute action.
--
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
On Mon, Feb 23, 2009 at 7:46 PM, Ville M. Vainio vivai...@gmail.com wrote:
act-on-node only makes sense if a plugin can be certain that it should
handle this. If you can't be certain by node itself (headline, body),
Additional note - if your plugin is written in such a way that it
can't
it will useful for amateur plugin makers
that only want to make simple plugins. As an example, think of being
able to prepend @done to p.h and pressing alt+a = node is moved to
done tree somewhere out of sight. You could make that with ~ 5 lines
of code.
--
Ville M. Vainio
http://tinyurl.com/vainio
, even if the node was just created by the user typing
ctrl-Icache.pyRET, so uAs don't work either.
How do you differentiate this with current active_path.py?
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
On Mon, Feb 23, 2009 at 8:19 PM, Ville M. Vainio vivai...@gmail.com wrote:
It can still apply in a limited form, where act-on-node reacts to:
More thoughts on this:
- The problem here is mostly a social one. The basic guideline is not
to write antisocial plugins that eat up act-on-node's from
On Mon, Feb 23, 2009 at 8:49 PM, Ville M. Vainio vivai...@gmail.com wrote:
On Mon, Feb 23, 2009 at 8:19 PM, Ville M. Vainio vivai...@gmail.com wrote:
It can still apply in a limited form, where act-on-node reacts to:
More thoughts on this:
And even more (it seems I'm postponing washing
to/from that set.
You can make that a high priority handler, since it's only enabled
when you want it to be enabled. There is no need to unload/reload
plugins to accomplish this (which necessarily demands less from the
plugins).
--
Ville M. Vainio
http://tinyurl.com/vainio
On Mon, Feb 23, 2009 at 7:05 PM, Edward K. Ream edream...@gmail.com wrote:
But if it solves problems for the qt gui, I don't mind trying it...
So do you want me to push it, or will you do it yourself?
--
Ville M. Vainio
http://tinyurl.com/vainio
(self,item):
@@ -3760,6 +3760,7 @@
def setHScroll (self,hPos):
w = self.treeWidget
hScroll = w.horizontalScrollBar()
+hScroll.setValue(hPos)
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message
:
It seems you put qt under leo-editor...
No, I don't think this will have any effect on how it will behave.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group
emacs-like composite commands like C-x r s i a).
--
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
still think this sucks for the likes of @url nodes. You
typically only select one, and then move on to other activities.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo
that node again would disable the mode, getting rid of the buttons and
disabling alt-a actions. This way, your mode would not clutter the
ui when it's not active.
I admit I'm not a great fan of modefull ui's in general, but it's a thought.
--
Ville M. Vainio
http://tinyurl.com/vainio
it up).
Response to multiselection on a new thread.
--
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
).
This is actually my pet gripes with leo currently - I hate deleting a
bunch of nodes with demote + cut.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
? If not, a half-assed hack could involve moving
selected items under one temp item, cutting/copying the temp item, and
demoting deleting the temp item on paste...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
collect-selected-nodes-as-children-of-this-node
(with a less out-there name), delete-selected-nodes, ...
QTreeWidget.selectedItems() is the method to call to implement these methods.
Unit tests pass.
--
Ville M. Vainio
http://tinyurl.com/vainio
On Tue, Feb 24, 2009 at 10:44 PM, Ville M. Vainio vivai...@gmail.com wrote:
Even if the existing commands don't scale to multiselection yet, new
commands can be added that operate specifically on multiple selected
nodes. Something like collect-selected-nodes-as-children-of-this-node
-to-code usability
without hooking explicitly to ui events. I see it as a general
solution, but you can only seek certain level of generality without
succumbing to analysis paralysis and over-engineering.
--
Ville M. Vainio
http://tinyurl.com/vainio
and compelling wording :-).
--
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
, // comments, /* comments */
- Python reserved words
- xml
--
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
it (cut-copy-paste) should be done.
As for the rest, leave the worry to those who need the feature the
most :-). Most of the time, we could do just fine with this brief
list.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
++
--
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
On Wed, Feb 25, 2009 at 7:33 PM, Ville M. Vainio vivai...@gmail.com wrote:
On Wed, Feb 25, 2009 at 7:15 PM, tfer tfethers...@aol.com wrote:
Have you looked at editra? Its a wxwindows based IDE in python. It
has lexer support for several languages and is written in python. Has
a BSD
On Wed, Feb 25, 2009 at 6:27 PM, Ville M. Vainio vivai...@gmail.com wrote:
I've been thinking of implementing a simple and fast lexer that would
work reasonably with most languages. Not perfectly, but reasonably
(i.e. enough for me). It would support
Here's a lexer that should be as fast
On Wed, Feb 25, 2009 at 8:32 PM, Ville M. Vainio vivai...@gmail.com wrote:
Here's a lexer that should be as fast in python as it's in C++ and
could be made pluggen in in quite a simple fashion:
... could be plugged in...
Sometimes on my minilaptop, I don't quite read what I type
.20090225204403.2:leoTrivialQtSyntaxHighlighter
#...@+node:ville.20090225204403.8:hook it up!
w = c.frame.top.richTextEdit
hl = leoTrivialQtSyntaxHighlighter(w)
#...@-node:ville.20090225204403.8:hook it up!
#...@-others
--
Ville M. Vainio
http://tinyurl.com/vainio
On Wed, Feb 25, 2009 at 9:03 PM, Ville M. Vainio vivai...@gmail.com wrote:
Here's how to change the syntax higlighter easily when leo is running:
w = c.frame.top.richTextEdit
hl = leoTrivialQtSyntaxHighlighter(w)
Where leoTrivialQtSyntaxHighlighter is just a subclass of
QSyntaxHiglighter
it as as plugin if/when it ever becomes worth its salt.
--
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
that doesn't work correctly. So they
have this function menu-bar-enable-clipboard which basically means
please make my cut and paste work correctly. Why is this an option?
I call this kind of preference the unbreak my application please
button. Just fix the app and be done with it.
QQQ
--
Ville M
On Thu, Feb 26, 2009 at 6:28 PM, Kent Tenney kten...@gmail.com wrote:
https://bugs.launchpad.net/leo-editor/+bug/322026
The qt gui doesn't allow deleting @buttons
I'll take a look
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You
to it instead of direct
widgets (the whole toobar api seems to prefer this). They look a bit
nastier now (due to context menu), I didn't look into fixing the looks
yet.
Unit tests pass, apart from the usual suspects (backlinks).
--
Ville M. Vainio
http://tinyurl.com/vainio
On Thu, Feb 26, 2009 at 12:11 AM, Ville M. Vainio vivai...@gmail.com wrote:
They may not be necessary soon, but they can be a useful thing to
have. Perhaps the size of the nodes we can view in color would improve
as well.
Think of this as an experimental highlighter in worse is better
where no
extensive restructuring of the files happens behind your back (e.g.
sort-siblings ;-). Thin nodes with explicit sentinels are needed when
such restructuring is happening.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
can abandon @thin nodes.
--
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
-nodes.
--
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
. Sigh.
Incidentally, my previous suggestion is very compatible with this
approach (use @auto for everything, but still allow cloning in
co-operative environment).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
On Fri, Feb 27, 2009 at 5:20 PM, Ville M. Vainio vivai...@gmail.com wrote:
We can create the gnx from the checksum of all of the node body (plus
full file path) when we do @auto parsing. That way, we could have
clones that survive re-reading of the @auto file, provided that the
function
relatively well, even if they don't really handle reordering
that spectacularly.
--
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
by @shadow? Or rather, the
@shadow be renamed to @auto?
If leo stored the private shadow files to ~/.leo, the clutter factor
of @shadow would be eliminated.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
like this is a special case of the
very same thing (which mostly proves that it's a good idea ;-).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group
-on-node is making plugins co-operate on
default action, so nodeActions can still play nice even if another
active plugin is interested in icon doubleclick activity.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
language in use).
I admit that now when the syntax highlighting for non-python languages
is fixed, I have much less interest in pursuing this little project.
Main motivation would probably be compatibility with Ubuntu Hardy,
which happens to be my work computer.
--
Ville M. Vainio
http
)
This will upcase the headline when it starts with @up.
--
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
On Fri, Feb 20, 2009 at 6:52 PM, Ville M. Vainio vivai...@gmail.com wrote:
I imported some files that use tabs for indentation with active_path
plugin. I noted that the tab size was huge.
QTextEdit has a way to specify tab stop width in pixels. I ran this
and tabs were sane again
stroke or qualified mouse click to a command.
I'd leave qualified mouse clicks alone, since they really belong to
multiselection mode.
Perhaps some kind of quick create @button for last complex command
would do the trick?
--
Ville M. Vainio
http://tinyurl.com/vainio
for introducing other scanners
easily, if you manage to integrate it in general enough fashion.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
, there is an annoying pause when you
just want to skip over a node. This could be solved by emitting the
selecthint on idle phase with some (0.2 sec?) delay when the node is
large, but I'm not at all sure how robustly it would behave w/ regard
to rest of leo (e.g. unittests).
--
Ville M. Vainio
http
I enter the @ character (because it colorizes all the following
text).
--
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
with an arm processor for extra saving.
Hibernating to hard drive works on computers these days, but my
understanding is that it has always been badly implemented.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
annoyance.
--
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
by definition
they get the last word. If you don't like that, don't call TryNext
in yoru high priority handler ;-).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor
On Fri, Mar 6, 2009 at 8:20 PM, Ville M. Vainio vivai...@gmail.com wrote:
I also believe we will see performance improvements to QTreeWidget, as
well as overall rendering speed improvements (esp. on Linux) - not
that I have noted any problems in rendering speed as such.
There are benchmarks
On Sat, Mar 7, 2009 at 10:45 PM, Ville M. Vainio vivai...@gmail.com wrote:
http://www.windowsfordevices.com/news/NS6339160832.html
Just compiling qt with -graphicssystem raster here ;-)
I don't recommend qt 4.5 yet - at least until a compatible pyqt is
really released. I had QBoxLayout
On Mon, Mar 9, 2009 at 8:12 PM, Edward K. Ream edream...@gmail.com wrote:
This would configure individual nodes - e.g. allow storing colors in
uAs, as in cleo plugin.
Oh. I'm with you now.
Should I push a demo implementation (few small changes to core a plugin)?
--
Ville M. Vainio
http
On Mon, Mar 9, 2009 at 10:15 PM, Ville M. Vainio vivai...@gmail.com wrote:
Should I push a demo implementation (few small changes to core a plugin)?
I have now pushed an example plugin necessary core mechanics to
trunk (and ran unit tests ;-).
Included is colorize_headlines.py, a plugin
at hand
(e.g. now I'm working on task bugfix_123, set interest db
accordingly). This is of course a piece of cake to implement by just
switching the interest db.
All in all, this should be pretty easy to do with what we have
currently. Now it just has to be done :-).
--
Ville M. Vainio
http
by:
c.find_h('Gui wrap.*').select(.*Qt).select('Font')
I can add it to trunk if it's ok for Edward / others.
Let's avoid function names like findNodeAnywhere_iter... they are an
absolute nightmare to remember.
--
Ville M. Vainio
http://tinyurl.com/vainio
and easy to use.
Edward?
--
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
On Wed, Mar 11, 2009 at 8:51 PM, Ville M. Vainio vivai...@gmail.com wrote:
I have now pushed the easy node searching stuff to trunk.
Some caveats should be noted:
- No extensive (or, well, non-extensive) testing has been done. Need
to apply in real plugins to flesh out the details.
- select_h
On Wed, Mar 11, 2009 at 9:17 PM, Ville M. Vainio vivai...@gmail.com wrote:
search for is at arbitrary (unknown) depth under parent. Arbitrary
depth traversal would need a smart implementation in order to avoid
scanning same nodes several times (to avoid bad performance
surprises
On Wed, Mar 11, 2009 at 9:49 PM, Ville M. Vainio vivai...@gmail.com wrote:
BTW, an unrelated thought - maybe select_b may not have the most
intuitive behaviour right now, since it looks at the *direct children*
of the nodes in poslist (just like select_h). Perhaps it should just
scan
On Wed, Mar 11, 2009 at 10:37 PM, Ville M. Vainio vivai...@gmail.com wrote:
There is also an annoying logical glitch - select_h is one step too
far in traversal, which will surely trip people expecting precise
selection of one node, as opposed to its children. Stay tuned, and
don't try
On 3/11/09, Ville M. Vainio vivai...@gmail.com wrote:
The surprising behaviour happens because select_h is actually 2
operations rolled into one:
Ignore previous statement, I spoke before debugging select_h properly.
At some point, I improved the implementation by using finditer
instead
On Thu, Mar 12, 2009 at 7:54 AM, Ville M. Vainio vivai...@gmail.com wrote:
On 3/11/09, Ville M. Vainio vivai...@gmail.com wrote:
The surprising behaviour happens because select_h is actually 2
operations rolled into one:
Ignore previous statement, I spoke before debugging select_h properly
, line 4453, in
toUnicode
return unicode(s)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd1 in position
Seems like calling unicode(chr(some_value)) is a bad idea...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
blank line.
Can you elaborate a bit on the background - why do @auto nodes need to
normalize the content somehow?
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo
, I'm not clear how it's different from @auto
from the user/collaboration standpoint.
You can make persistent metadata changes to @shadow files (introduce
hierarchy, change headlines etc), without the guy next to you ever
seeing that on his own computer ;-).
--
Ville M. Vainio
http://tinyurl.com
for el in all_bm))
Just do the same in C (which I mostly code with currently) ;-)
--
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
global settings).
Note that these settings, like shadow files, would not be meant to be
shared with others at all. They can also be useful as caches.
I would do all the work for making this available, of course.
--
Ville M. Vainio
http://tinyurl.com/vainio
these days - but this seems quite possible,
since leo is only able to run when readline is yielding time for tk
mainloop. There is an interesting deadlock here :-).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because
On Thu, Mar 12, 2009 at 9:07 PM, Ville M. Vainio vivai...@gmail.com wrote:
Now that I played with the select_h set of iterators, I must say
they are definitely the most fun way to walk through leo outlines.
There is one optimization that I think would be worth making - in
addition to find_h
, ...
--
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
diffs loud complaints.
--
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
as possible -
reduces the initial I can't use leo to make a small change to one
function reaction.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
.
c.db is a general-purpose persistent dictionary, right?
useful for settings, but available for any kind of data storage?
Yes. Everything that can be pickled can go in.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message
, leo.external (where simple third party
contributions should go). I *copied* path.py there and added
pickleshare.py. path.py is still in extensions/, but that is not a
real package and an 'external' package fits this purpose perfectly. We
did the same move on ipython long time ago.
Have fun!
--
Ville M
vnode. Now that I think of it, wouldn't unique vnode
id's provide a more robust (archived) representation of positions than
just node indices? Perhaps a form like foo.bar.baz where every element
is a vnode id.
--
Ville M. Vainio
http://tinyurl.com/vainio
On Fri, Mar 13, 2009 at 7:08 PM, Ville M. Vainio vivai...@gmail.com wrote:
The database is in /foo/bar.leo_db dir if you want to browse it.
Make that /foo/.bar.leo_db (note the leading period)
(bzr pull).
This is analogous to ~/.leo, ~/.bzr etc. so we should probably follow
that convention
On Fri, Mar 13, 2009 at 7:29 PM, Ville M. Vainio vivai...@gmail.com wrote:
it refers to same vnode. Now that I think of it, wouldn't unique vnode
id's provide a more robust (archived) representation of positions than
just node indices? Perhaps a form like foo.bar.baz where every element
one document).
they'd essentially have the same livespan as v.u?
Yes, serialized in xml, etc.
Also, there would always be available a vnode id = vnode dict for
fast discovery (for all plugins, no point in backLinks having its own
id dict).
--
Ville M. Vainio
http://tinyurl.com/vainio
here:
http://ipython0.wordpress.com/2008/05/15/embedding-ipython-in-gui-apps-is-trivial/
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
(for the duration
of execution)
- You get syntax highlighting for everything because it's scintilla.
E.g. bzr diff output is higlighted.
- Sane multiline editing (e.g. defining functions)
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
... is there
somebody out there, who can tell me something about that all?
- Do not use Python 3.x versions yet. Very few downloadable programs
work with that
- Start leo with launchLeo.py (from source), do not use any kind of installer.
--
Ville M. Vainio
http://tinyurl.com/vainio
code
related to indentation etc.
--
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
the archived
positions, provided that we didn't really make the node disappear.
Ergo, no need to keep updating a database all the time.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On Sat, Mar 14, 2009 at 5:22 PM, Ville M. Vainio vivai...@gmail.com wrote:
This path still points to the same file, even when we delete
/foo/bar/blah.txt. Equally, we could have
/12/45/111
and
/1321/112/45/111
Also note that we don't need to change the core all *that* much - just
add
vnode
- If that fails, the node is deleted.
While we are at it, perhaps it might also make sense to move
headstrings to tnodes?
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On Sun, Mar 15, 2009 at 5:50 AM, Jesse Aldridge jessealdri...@gmail.com wrote:
Is there a way to stop a script activated via a script button? For
example if it's hung in an infinite loop. (Other than killing leo.)
Press ctrl + c on the console where you ran launchLeo.
--
Ville M. Vainio
, ...). Multiselecting a range of items is
much handier if you avoid blinking the body control with the hits
every time.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group
On Mon, Mar 16, 2009 at 2:07 PM, Edward K. Ream edream...@gmail.com wrote:
Can I safely bzr ignore these files, or should they be part of bzr
commits?
Definitely bzr ignore them.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
--
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
')
pos = pl[0]
c.executeScript(pos)# or whatever is the way to do ctrl+B on a
specified position
# test cases...
c.executeScript(pos)# or whatever is the way to do ctrl+B on a
specified position
# more test cases...
--
Ville M. Vainio
http://tinyurl.com/vainio
+f by default. Mouseless quicksearch
is now a breeze :-).
--
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
'...
--
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
On Tue, Mar 17, 2009 at 7:21 PM, Ville M. Vainio vivai...@gmail.com wrote:
I've wanted to support refactoring in Leo for a long time. All ideas
welcome.
May be hard, though leo might be used to *drive* refactoring of a code
elsewhere. There is 'rope' and 'bicyclerepairman'...
Leo has
.
Luckily, almost everything here is easy to do in plugins.
--
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
401 - 500 of 2371 matches
Mail list logo
