"Edward K. Ream" <[EMAIL PROTECTED]> said on Jun 03, 2008 10:09
-0400 (in part):
> So Leo is getting ever closer to the point at which I will declare it
> complete.
Don't do that Edward! I've been following Leo as an interested on-looker
into the process of developing software, though not as a
I think push is inherently dangerous - you should only ever need to use
it once on a launch pad branch, to create the branch.
After that I'd use a bound checkout, so that when you commit bzr checks
for changes and refuses to do anything until they're merged.
bzr init-repo leo.repo
cd leo.repo
b
The bzr FAQ does a nice job describing the work flow based on a
"Hosted" branch which is peer reviewed and then merged into the
trunk. What about small code changes or documentation changes?
Should these type of changes also follow the peer-reviewed work flow
described in the FAQ or should there
Thanks Edward and Ville,
Very helpful!!!
TL
--~--~-~--~~~---~--~~
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 em
I pushed my changes to the trunk but it looks like I was only at rev
479 but the trunk was at 481. Edward, do you wan't to restore your
changes or should I do something?
TL
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gr
I can't work this out...
@enabled-plugins found in myLeoSettings.leo
Traceback (most recent call last):
File
"/media/usr1/usr1/home/tbrown/.gnome-desktop/Package/leo/bzr/leo.repo/trunk-test/leo/core/leoPlugins.py",
line 221, in loadOnePlugin init_result = result.init()
File
"/media/usr1/usr
Ville recently reposted (to an ipython list) his tutorial about how to
use bzr. I copied it to Leo's FAQ:
http://webpages.charter.net/edreamleo/FAQ.html#how-do-i-use-bzr-to-get-the-latest-sources-from-leo-s-launchpad-site
And it's in LeoDocs.leo on the trunk. Thanks Ville for this very
clear e
On Tue, 3 Jun 2008 13:23:45 -0500
"Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> There appear to be big problems with rClick.py. It segfaults on Linux
> when I right click in the body pane. Even when disabled, there is a
> crash in setDefaultContextMenus. More work is needed.
Thanks, disabled i
On Tue, Jun 3, 2008 at 9:23 AM, Terry Brown <[EMAIL PROTECTED]> wrote:
>
> Cleo's context menu does this:
>
> Error: 1
> Exception in Tk callback
> Function: (type: 'function'>) Args: (,)
> Event type: ButtonPress (type num: 4)
> Traceback (innermost last):
> File
>
> "/home/tbrown/Desktop/P
Vi's command mode blockcursor <==> insert mode's 'beam' cursor.
TK 8.5 supports a -blockcursor option, but playing with this requires
a Tkinter
updated to work with 8.5. That is rumored to be slated for python 2.6
and/or 3.0.
Hopefully it is possible to shift back and forth between the two in a
On Tue, Jun 3, 2008 at 6:31 PM, TL <[EMAIL PROTECTED]> wrote:
> bzr: ERROR: Cannot lock LockDir(http://bazaar.launchpad.net/%7Eleo-
> editor-team/l
> eo-editor/trunk/.bzr/branch/lock): Transport operation not possible:
> http does n
> ot support mkdir()
You must use bzr+ssh protocol instead of h
On Tue, Jun 3, 2008 at 10:31 AM, TL <[EMAIL PROTECTED]> wrote:
>
> I'm trying to update the trunk with a fix to the mod_tempfname.py
> plugin.
> The following commands result in a "Cannot lock LockDir" error.
> How can I avoid this?
I define the following two aliases in bazaar.conf:
unlock=brea
On Tue, Jun 3, 2008 at 10:03 AM, Terry Brown <[EMAIL PROTECTED]>
wrote:
>
> trunk-test>
>
> PYTHONPATH=$PYTHONPATH:/home/tbrown/Desktop/Package/leo/bzr/leo.repo/trunk-test
> python launchLeo.py Traceback (most recent call last): File
> "launchLeo.py", line 6, in leo.core.runLeo.run()
> File
>
>
On Tue, Jun 3, 2008 at 12:00 PM, TL <[EMAIL PROTECTED]> wrote:
>
> This post is in response to Edwards request for guidence on what vi
> problems should be fixed first. Each problem is documented in a sub-
> branch from this post.
Thanks for this. I'll put all three problems on the list and ge
Commands getting user input (Medium problem / moderate to fix?)
Any commands that request user input will exit the mode immediately
after the input is received. This prevents vi commands that will copy
or replace text up to a user specified character. For example, key
sequence 'stw' should "Sub
Editing headlines within modes (Major problem / Difficult to fix?):
Commands that modify or select headline text correctly when bound
directly to a key will, when executed from within a mode bound to that
same key, modify or select the body text. This prevents most of vi's
delete, change, substi
Focus to Body pane (Major problem / Easy to fix?):
Modes always return with the focus put to the body pane even if edit-
headline command was called. This prevents most node navigation and
editing commands from working. The problem is due to the exit-named-
mode command, which is used in most
This post is in response to Edwards request for guidence on what vi
problems should be fixed first. Each problem is documented in a sub-
branch from this post.
Note; Most of the vi related problems are documented in the "Vi
documentation" node in the leoSettings.leo file.
--~--~-~--~
On Tue, Jun 3, 2008 at 8:56 AM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
>
> From my point of view, paying for vim bindings worked out well: the
> result is clearly much more "vim-like" than I would have created.
>
> However, I want to make sure that the reward causes no resentment or
> other har
I'm trying to update the trunk with a fix to the mod_tempfname.py
plugin.
The following commands result in a "Cannot lock LockDir" error.
How can I avoid this?
bzr branch lp:leo-editor
bzr merge
< modified leo\plugins\mod_tempfname.py >
bzr commit leo/plugins/mod_tempfname.py
bzr push lp:leo-
On Tue, Jun 03, 2008 at 06:56:34AM -0700, Edward K. Ream wrote:
>
> >From my point of view, paying for vim bindings worked out well: the
> result is clearly much more "vim-like" than I would have created.
>
> However, I want to make sure that the reward causes no resentment or
> other hard feeli
trunk-test>
PYTHONPATH=$PYTHONPATH:/home/tbrown/Desktop/Package/leo/bzr/leo.repo/trunk-test
python launchLeo.py Traceback (most recent call last): File
"launchLeo.py", line 6, in leo.core.runLeo.run()
File
"/media/usr1/usr1/home/tbrown/.gnome-desktop/Package/leo/bzr/leo.repo/trunk-test/leo/core
Cleo's context menu does this:
Error: 1
Exception in Tk callback
Function: (type: ) Args: (,)
Event type: ButtonPress (type num: 4)
Traceback (innermost last):
File
"/home/tbrown/Desktop/Package/leo/bzr/leo.repo/trunk/leo/extensions/Pmw/Pmw_1_3/lib/PmwBase.py",
line 1747, in __call__ retu
There are about 15 bugs on the to-do list. I plan to release Leo 4.5
b1 after fixing all or most all of those bugs. This will probably
happen in about a week.
After that, there will be 2 or 3 weeks of additional work and testing
before Leo 4.5 final.
After Leo 4.5 final, there are only a two m
The trunk now contains a version of the cleo plugin that honors the
@bool cleo_color_ignore = True
setting. The legacy behavior is as shown, and leoSettings.leo now
contains this setting. I added this setting because I don't like
coloring special headlines, including @ignore nodes, so I set th
>From my point of view, paying for vim bindings worked out well: the
result is clearly much more "vim-like" than I would have created.
However, I want to make sure that the reward causes no resentment or
other hard feelings among all those who have made so many
contributions to Leo for free.
You
On Jun 3, 5:49 am, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> Moving on, the following is indeed a bug, and I plan to fix it soon:
>
> QQQhttp://sourceforge.net/forum/forum.php?thread_id=1858451&forum_id=10228
>
> If I create a @settings->@menus->@menu node in a file, open
> the file, then o
On May 9, 1:06 pm, Terry Brown <[EMAIL PROTECTED]> wrote:
> > Leo will read myLeoSettings.leo twice if that's the file you are
> > actually opening. It's not worth "fixing".
>
> It's not the file I'm actually opening, it's $HOME/myLeoSettings.leo
> and $PWD/myLeoSettings.leo (using $PWD as not
On Wed, May 28, 2008 at 9:06 AM, Kent Tenney <[EMAIL PROTECTED]> wrote:
>
>> OK, I'm using --one-config, so there is no mystery
>> surrounding the source of settings.
>>
>> I'm discovering the following
>>
>> - top level @menus can be commented out with @@menu
>> - secondary level menus cannot
>>
29 matches
Mail list logo
