On Apr 8, 11:26 pm, TL [EMAIL PROTECTED] wrote:
Edward, I want to make you aware of some work that I have done to
improve (imo) the use of Vim with Leo. [snip] I have
implemented support for the use of Vim's tabs and the automatic
placement of the Vim cursor on the same line as the Leo
Gulp! I guess I'm out of my depth on this one. I'll find something
easier to do!
Bob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to
Whoops! Looks like I've stirred up a can of worms! My excuse is that
you did ask us to bang on the code :)
Bob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to
find-word is such a useful command that I added a variant: find-word-
in-line. The former now finds the next word anywhere in the (usually
body) text. The latter limits the search to the present line.
Yes, thank you, thats much more useful.
On Apr 8, 11:26 pm, TL [EMAIL PROTECTED] wrote:
With some modifications to the Open With plugin, I have
implemented support for the use of Vim's tabs and the automatic
placement of the Vim cursor on the same line as the Leo cursor wen the
file is first opened in Vim.
Ok TL, give me a
On Apr 8, 4:54 pm, Edward K. Ream [EMAIL PROTECTED] wrote:
On Apr 8, 9:35 am, Edward K. Ream [EMAIL PROTECTED] wrote:
The present code is just about too difficult to understand.
That makes me feel better, I tried to fix this myself before reporting
it, thinking it was an easy fix, but got
On Apr 8, 3:43 pm, Edward K. Ream [EMAIL PROTECTED] wrote:
I want to encourage people to use the bzr trunk.
Thats a great idea, installing bazaar is so easy, and downloading and
updating leo so simple that any other method of getting leo is quite
complicated in comparison.
I would like to
On Wed, Apr 9, 2008 at 6:28 AM, bobjack [EMAIL PROTECTED] wrote:
Whoops! Looks like I've stirred up a can of worms! My excuse is that
you did ask us to bang on the code :)
It's important to fix these bugs. In spite of complications, the final code
is localized and relatively clean. I'll
On Tue, Apr 8, 2008 at 7:09 PM, vpe [EMAIL PROTECTED] wrote:
TL [EMAIL PROTECTED] wrote:
These changes have given me a very usable Vi capability that works
well with Leo. As a result, it is not as important to me that Leo
have a full featured Vi editor emulated.
I am sceptical about
On Wed, Apr 9, 2008 at 4:37 AM, bobjack [EMAIL PROTECTED] wrote:
On Apr 8, 3:43 pm, Edward K. Ream [EMAIL PROTECTED] wrote:
I want to encourage people to use the bzr trunk.
Thats a great idea, installing bazaar is so easy, and downloading and
updating leo so simple that any other method
On Tue, Apr 8, 2008 at 4:27 PM, TL [EMAIL PROTECTED] wrote:
Now that 4.4.8 has been released, I hope someone can spend a little
time helping to get me up to speed on some development issues. I have
some questions about the setup of Bazaar and the handling and merging
of local modifications
Leo's trunk now contains the fixes for the how-many, find-word and
goto-character commands, as well as a fix for the find completion
problem.
Alas, tab completion for commands is broken.
I think I'll use this as an opportunity to see how bzr can deal with
mistakes :-) I'll push the present
Popurls lead me to this yesterday:
http://code.google.com/appengine/
This is going to be big. Guido has been active in the project.
Anyone interested in web apps should take a look.
The main page has links to videos. The getting started guide might be
more useful:
I added a short bzr guide to LeoDocs, but didn't push it yet (because
the trunk was reverted). Here is the guide
(with some hard-earned information ;-), it will be on trunk later.
-
Many users will want to track the development version of Leo, in order to stay
on top of
On Apr 9, 8:54 am, Edward K. Ream [EMAIL PROTECTED] wrote:
I'll reinstate your recent change to LeoDocs.leo in a moment or two.
Done in rev 305.
Sorry for any inconvenience, but I really did want to play with
revert, etc. And it's important that major work be done in ekr-devel
rather than
On Apr 9, 8:58 am, Ville M. Vainio [EMAIL PROTECTED] wrote:
I added a short bzr guide to LeoDocs, but didn't push it yet (because
the trunk was reverted).
Thanks *so* much for this. Feel free to push it now.
Edward
--~--~-~--~~~---~--~~
You received this
On Wed, Apr 9, 2008 at 8:12 AM, TL [EMAIL PROTECTED] wrote:
How about using the Leo Wiki to document Bazaar and other Leo
development related issues? This would allow anyone to contribute and
the content to mature over time.
Sure. I invite you to add a page :-)
Edward
Edward, My fix to the FileActions plugin broke its support for @file-
ref. I also noticed that the plugin does not correctly handle @file
node types with spaces in the file name. I am willing to push the fix
for this into the trunk later today. Otherwise you can do it. Here
are the changes:
Thanks for the help! I needed it. You refer to issuing bzr
checkin. I think this should be bzr commit. Correct?
TL
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send
The trunk now contains a potentially significant change: the .use_sax
ivar in leoFileCommands.py is now set permanently to True.
This is the first step in the eventual removal of all the ancient hand-
coded read logic for .leo files. It's about 5 years overdue.
All unit tests pass, but there
On Wed, Apr 9, 2008 at 11:23 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
Thanks for the help! I needed it. You refer to issuing bzr
checkin. I think this should be bzr commit. Correct?
checkin and ci are aliases for commit.
I didn't know that :-)
Personally, I always use ci
On Wed, Apr 9, 2008 at 11:54 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
log=log -r -5
Oops. This should probably by log=log -r -5..
That is, the line should end with two periods.
EKR
--~--~-~--~~~---~--~~
You received this message because you are
I've been a leo user for almost two years, usually keeping up with
development through the _final.zip's on SourceForge. Since my main
environment is Linux, having myLeoSettings.leo not be a hidden file
was always annoying. So, each time I upgraded leo, I changed the
filename to
On Apr 9, 5:45 pm, thyrsus [EMAIL PROTECTED] wrote:
How much memory do you have? I rely on the python internals to
rapidly reclaim the dictionaries I create, but perhaps there should be
a line of code explicitly discarding the dictionary just before
raising the iteration ended exception.
I never dreamed that bzr would make such a difference to the Leo
project. The energy level and the level of collaboration are both
markedly greater today than they were a week ago. We now have a true
partnership of developers. This has been one of my dreams for Leo.
The more I play with
On Apr 9, 5:26 pm, thyrsus [EMAIL PROTECTED] wrote:
Explicitly doing self.d = {} right before raising StopIteration had
no significant effect for me. I saw that done somewhere else in the
code to provoke more rapid memory reclamation, but it doesn't seem to
make a difference in this
On Wed, Apr 9, 2008 at 5:15 PM, Dan White [EMAIL PROTECTED] wrote:
I've been a leo user for almost two years, usually keeping up with
development through the _final.zip's on SourceForge. Since my main
environment is Linux, having myLeoSettings.leo not be a hidden file
was always annoying.
27 matches
Mail list logo
