Hello, updated from Rev 3031 to 3793 - 1 issue

[TL]

Hello Edward, Ville, and old time colleagues.  I went underground for
a while to develop software tools and programs (using Leo of course).
As part of that endeavor, I decided to freeze my development
environment including Leo.  A few days ago I came up for air and
decided to try the latest Leo revision.  I updated to Revision 3793 a
few days ago and so-far-so-good except for one minor issue.  I'm using
Tk with Python 2.6.5.

At Leo startup, I receive the following error message followed by the
same error message repeated 9 times with the log-1 in the exception
binding Key+U to log-1 text replaced by the following: status-
line, canvas, bindingWidget, minibuffer, body-pane,
63379016, log-2, bindingWidget, bindingWidget,
bindingWidget, and bindingWidget.  The program appears to run
fine.  The error messages disappear if I remove the Vi/Vim emulator
key mappings from the MyLeoSettings.leo file suggesting that it is
related to the remapping of the u key to Vi's undo command.  The
remapping works.  I'm just hoping to remove the error messages.  Any
ideas?

Thanks, TL
---
Traceback (most recent call last):

  File c:\_Path\Leo\Trunk\leo\core\leoKeys.py, line 1937, in
makeMasterGuiBinding
c.bind(w,bindStroke,masterBindKeyCallback)

  File c:\_Path\Leo\Trunk\leo\core\leoCommands.py, line 6100, in
bind
w.bind(pattern,bindCallback,*args,**keys)

  File C:\Program Files (x86)\_Dev\Python2.6\lib\lib-tk\Tkinter.py,
line 985, in bind
return self._bind(('bind', self._w), sequence, func, add)

  File C:\Program Files (x86)\_Dev\Python2.6\lib\lib-tk\Tkinter.py,
line 940, in _bind
self.tk.call(what + (sequence, cmd))

TclError: bad event type or keysym Key+U

exception binding Key+U to log-1

-- 
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: Code mode must go? Was second draft of rst3 tutorial

[TL]

Hi Edward,

Long time no post.  As you may remember, I use @rst to develop html
pages for the web and for use in .chm help files (same content
tailored to each environment).  I'm nervous about your plans to make
changes to the way that @rst works.  I don't know if the features I
use will be affected by your changes but I certainly appreciate
pressing one button and having ~20 html files created from leo nodes.
I will try to find time this weekend to send you a Leo file that shows
my @rst environment.  I hope that will provide you with some insight
as to how I'm using it.

Note: I have been so busy developing software with Leo lately that I
haven't had time to update to the latest version since March.

Regards,
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-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 clones in external files, safely

[TL]

The multifile plugin also provides a means to store a second copy of a
file in another directory.

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-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: The right kind of magic

[TL]

Many editors provide the ability to fold lines; in effect, hiding
lines when editing the file.  I have set up my Vim editor to fold
sentinels into a single line that is displayed as a series of
hyphens.  Here are the commands to configure this in the _vimrc file:

FOLDS - Setup folds to hide Leo's sentinels
Specify expression based folds
set foldmethod=expr
Specify expression to use to denote a sentinel line (2nd char in line
a '@')
set foldexpr=getline(v:lnum)[1]==\@\
Specify that all consecutive sentinels are folded into single line
set foldminlines=1
Show a row of hyphens when folded
set foldtext=v:folddashes

Regards,
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-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.

Vim improvements within Leo

[TL]

Edward, I suggest you initially focus on implementing the original
features in the Vi editor.  Additional Vim features can be added as a
Phase 2.

During the development of the current Vi implementation, I documented
many of the Vi features that could not be implemented in the Vim
Developer Documentation node in the leoSettings.leo file.  See the
Open issues section within the body text.

Let me know how I can help?

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-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: @Chapters not working?

[TL]

Like Ville, I just open it from the Help menu.  Does that work for
you?

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-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.

nodeActions plugin updated

[TL]

Rev 3059 has a small update to the nodeActions plugin to allow pattern
matching nodes under the nodeActions node to be at any sub-level.
This allows related patterns to be placed under a common node or to
place patterns that you want to include in multiple Leo files to be
stored in an external file and loaded using an @thin node.  For
example:

+- nodeActions
   |
   +- @thin C:\Leo\nodeActionsPatterns.txt
  |
  +- http:\\*
  |
  +- @thin *.py

See the documentation in Chapter 12 of Leo's User Guide for more
information at:
   http://webpages.charter.net/edreamleo/plugins.html#nodeactions-py

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-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.

Remapping keys in Linux

[TL]

A problem with Vim emulation was posted in the leo-editor-users
suggestiing that key bindings are not working under Linux.
They receive the redfining shortcut messages in the log file that is
normally seen when the emulation remaps the keys but the new mappings
aren't working.  Can anyone confirm that there is a problem or no
problem
with key bindings in Linux?

See the post at:
  
http://groups.google.com/group/leo-editor-users/browse_frm/thread/0b0b7e105c46292f#

Thanks,
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-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: code bubbles

[TL]

 I guess there may be a way to do this with clones --
 but how to do that without creating orphans?
 I don't want to -include- the dragged node with the
 other node -- just put it nearby so I can look at both
 of them at the same time easily.

The Leo approach, as I understand it, is to create a separate node
representing the current task your working on and place it outside of
the nodes that generate files (like @thin nodes) and then create
clones of the nodes associated with that task and drag or copy-paste
them under the new task node.  With this method you don't effect the
contents of the files exported by Leo.

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-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: code bubbles

[TL]

 A side effect of this approach is getting redundancy in the
 version control system (which includes the .leo file too).

Assuming you don't check in the files until the task is completed you
could delete the task node and its sub-nodes before the check-in.

If you want to retain a reference in the Leo file of the completed
task without having the contents of the cloned sub-nodes in the Leo
file, you could use the body of the task node to document the task
that was performed with a list of the nodes that we're effected and
then delete the clones.

It would not be too difficult (for a Leo guru) to create a script
that, when invoked on the Task node, would traverse its sub-nodes
and, for each clone found, append the clone's headline to the end of
the Task node's body text along with the hierarchical path to the
clone's base node.

For example, if the original tree looks like this:

   Application
  @thin mainProg.py
 func1
 func2
   Website
  @rst homePage.htm
 header
 contents
 tail

and you create a task node with clones of the func2 and contents
nodes then the script could automatically append the following (or
some other variation) in the Task node's body:

   Referenced nodes:
  func2 : @thin mainProg.py  Application
  contents : @rst homePage.htm  Website

You could even create a script that would restore the clones under the
task node based on the list.

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-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: Scripting question

[TL]

 I need to gather siblings above the node with focus.

I assume this refers to the node's parent's siblings.  Or perhaps we
could just say the node's aunts and uncles :-)

-- 
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.

Auto newline at end of file - annoyance

[TL]

When editing a Docutils file in an external editor (exported from
Leo), I always get a Replace changed outline with external changes?
dialog box when I save the file in the external editor.  This appears
to occur because a newline is added to the end of the file when it is
imported back into Leo.

Note: The addition of a newline occurs even if the imported file
already has a newline at the end of the file.

There appears to be two problems:

1) Leo always adds a newline even if the already has one.
2) After Leo has added the newline it mistakenly marks the buffer as
modified.

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-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.

Vim emulation update

[TL]

Leo revision 3031 contains the following changes (tested with Tk GUI):

Keys 'j' and 'k' will scroll the text in the body pane when the cursor
focus is in the outline pane.  It is currently implemented using Leo's
next-line and previous-line commands (body scroll commands don't
work within a mode node).  As a result, scrolling won't occur until
the cursor moves to the end or beginning of the visible text.
Hopefully, body scroll commands will be fixed to work within mode
nodes soon.

Fixed problem when inserting characters into first column in first row
in the body pane causing the cursor focus to switch to the node's
headline.

Chapter 22 of Leo's user guide updated to reflect recent changes.

Let me know if you find a problem.

Regards,
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-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: Browser-like binding

[TL]

The Vim emulator has been supporting the ability to scroll the body
pane and move between nodes while keeping the cursor focus in the body
pane.  The latest update to the Vim emulator now supports the same
capability while keeping the cursor focus in the outline pane.

Unlike your proposal, both implementations use separate keys bindings
for the body scroll and the next/previous node functionality.

See the Vim emulation documentation and the following post for more
information:

http://groups.google.com/group/leo-editor/browse_thread/thread/58cb883a89d3816a#

Regards,
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-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: Vim emulation update

[TL]

Edward, can you build the website's HTML file for chapter 22 of the
user guide?

Thanks,
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-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: persistent tree status required

[TL]

 Done at the trunk at rev 2974.

Is change only supported in the Qt gui?  Testing in the Tk gui results
in open sub-outlines being closed.

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-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: Clone headline mods not propagated (not fixed)

[TL]

Change to the headline of a node under a cloned node is still not
propogated to the same node under other copies of the parent cloned
node until a refresh of the outline occurs.  Bug has been reopened.

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-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/db files

[TL]

I just noticed that my .leo/db directory is consuming 17MB of storage
with 64 1st level sub-directories and 2,640 total files.  I believe
all of my project.leo files contain only @thin nodes or simple
nodes that are stored within the file.  What information is being
stored in the .leo/db files?  Are they just temporary files?  If so,
shouldn't Leo delete them?

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-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/db files

[TL]

Thanks zpcspm,

I should have searched the forum before posting.  My bad!

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-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/db files

[TL]

 The short answer is ...
 I shall soon merge ...

Thanks for clarifying this.  It looks like this issue is already on
the ToDo list.

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-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.

Clone headline mods not propagated (not fixed)

[TL]

I added a comment to bug 518823 but there doesn't appear to be a
method for me to reopen the bug so I'm posting here to be sure that
the problem is visible.

In the Tk plugin (an maybe Qt), changing the headline of a clone or a
sub-node of a clone does not change the headline of its clones until a
refresh of the outline occurs.

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-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: exception when using double-click to highlight headline for rename

[TL]

 1. The open_with plugin now demands that the Tk gui be present.  This
 probably will prevent the open_with plugin from loading unless Tk is,
 in fact, the active gui.

Isn't the open_with plugin required for exporting nodes to an external
editor in the Qt gui?

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-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: Warning: the trunk will soon have temporarily dubious open-with code

[TL]

Tested the open-with and the mod_tempfname plugins with Leo Rev 2868.
No problems found.

Thanks,
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-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: What to do with mod_tempfname plugin?

[TL]

 Am I correct in assuming that this requirement arises because you are
 looking at the file name in vim?

Yes.  I look at the file name to determine which node, of the
currently exported nodes, is the one that I'm working on or want to
start working on.  Vim looks at the file name's extension to determine
what syntax highlighting to apply.

Thanks for upgrading this code.  Python is not my native programming
language.  Any Why did he do it that way? questions that arise while
you working with the code is likely because I used the first solution
I could find, not the best solution.  At least the code has some
documentation :-)

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-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: Invalid path created for linked stylesheets

[TL]

 Done at rev 2789.  The rst3 command works and all unit tests pass.

Thanks.  Very much appreciated.

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-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 delayed until critical issues fixed

[TL]

 In such situations it is *hopeless* to expect the user to do something
 reasonable.  My typical reaction is, oh shit, what do I do now?.
 This is not the time for complex decision making!
 So we can't assume the user will do *anything*, and certainly not
 anything reasonable :-)

I don't agree.  Once a user chooses to put clones in @files that may
be edited externally, they take on a responsibility to address the
potential problems that could arise.  The last thing I want is for Leo
to guess at the appropriate resolution.  Instead, users should be able
to compare the differences and decide if I should keep them uncloned
or reclone them with either the old content, the new content, or a
some combination.  I don't think a user who has already taken on the
responsibility for managing Leo content (and the use of clones) will
classify this as complex decision making.

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-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 delayed until critical issues fixed

[TL]

 2. I suggest that variant versions of a clone get uncloned; it
would be useful to generate a warning

I think this is the best solution.  For a warning I suggest Leo create
a Node at the top of the Leo file with the headline Warning - Clone
conflict and child nodes that are clones of each uncloned node.  This
would allow the user to easily see what clones were uncloned and do
what was necessary to resolve the issue.  It would also be nice to
have a diff node plugin that could be used to easily determine what
differs between the uncloned nodes.

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-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: b2 coming Friday Please hold commits

[TL]

In a previous post I mentioned the following function that was
recently broken.  Any chance it can be fixed in b2?  The problem was
seen in the Tk.  I didn't check it with Qt.

The toggle-extend-mode function was broken somewhere between revision
2559 and 2669.

In responding to Gil's posting concerning key mappings associated
with
Leo's visual mode, I noticed that the toggle-extend-mode command no
longer works.  It displays the extend mode on when invoked but does
not select text when the cursor is moved.

Thanks,
TL


problem.  I assume it is an easy fix

On Jan 18, 9:22 am, Edward K. Ream edream...@gmail.com wrote:
 I plan to release Leo 4.7 b2 on Friday.  I will be doing only bug
 fixes and other release-related tasks until then.

 Please do not commit to the trunk until then without my permission.
 This will allow us all to test the trunk as thoroughly as possible.

 Thanks for your patience.

 Edward
-- 
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 bugs that would prevent Leo 4.7 b2 ?

[TL]

 As a non-vim user (yet) I don't understand this page.  Is there
 anything in particular I need to know or do?

No.  Gil is using some custom key mappings in his gVim editor.  He can
implement the same custom key mappings in his myLeoSettings.leo file.

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-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 bugs that would prevent Leo 4.7 b2 ?

[TL]

I am also a gVim user on Windows but my keys work as described in the
gVim help files.  I've searched again for a reference to your binding
in the help files without luck.  Let me know if you find anything.

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-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 bugs that would prevent Leo 4.7 b2 ?

[TL]

 Might I suggest the following non-bugs but very convenient and VIM 
 Windows compatible changes to @shortcuts - vi in Body pane:

The official Vim bindings for the keys you want to map are:
   Ctrl-x : Decrement the number under the cursor
   Ctrl-c : Interrupt current search command
   Ctrl-v : Start visual mode (blockwise)

If you want to create custom mappings for these then create a sibling
@keys My bindings node below the @keys Vim bindings node in your
myLeoSettings.leo file and define your custom bindings in it's body.
Your key bindings should replace any previously defined bindings for
the keys.  Let me know if you have a problem.

Note: Vim defines the 'd', 'y', 'p' keys to delete, yank, and paste
text when text has been highlighted (Leo's visual mode).  Because Leo
currently doesn't support separate key bindings when in visual mode,
the Vim emulator currently uses 'dcr' and 'ycr' instead of 'd' and
'y'.  The paste command doesn't have any multi-key variants so 'p'
works correctly in the Vim emulator.

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-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 bugs that would prevent Leo 4.7 b2 ?

[TL]

The toggle-extend-mode function was broken somewhere between revision
2559 and 2669.

In responding to Gil's posting concerning key mappings associated with
Leo's visual mode, I noticed that the toggle-extend-mode command no
longer works.  It displays the extend mode on when invoked but does
not select text when the cursor is moved.

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-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 bugs that would prevent Leo 4.7 b2 ?

[TL]

 I am going to add all the easy vim-related bugs to the list of things
 to do before b2.

The Fix headline undo problem appears to be fixed; possibly with the
code changes made to fix the node delete undo problem (Bug 498692).

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-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 bugs that would prevent Leo 4.7 b2 ?

[TL]

 Bug 439746 Leo crash with open_with plugin

I haven't seen the problem occur for awhile.  I suggest closing it.

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-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.

Bazaar Explorer - Repository view

[TL]

Anyone using the Bazaar Explorer plugin for bzr?
See: http://wiki.bazaar.canonical.com/BzrExplorer

It refers to a Repository view that can show what has changed to the
Trunk since your branch was last updated.  However, the documentation
doesn't show how you can create a Repository view of the Trunk on
LaunchPad (i.e. the lp:Leo-Editor repository).  Is it possible?  How?

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-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.

bzr problem and solution (rich-root-pack, Bazaar Explorer)

[TL]

On 12/19 I received the following error when I tried to pull the
latest Leo version:

  bzr: ERROR: Unknown repository format: 'Bazaar repository format
2a
  (needs bzr 1.16 or later)\n'

I updated bzr to version 2.0.3-2 (the standalone package) without any
luck.  However, the new bzr came with a Bazaar Explorer, a plugin
providing a windows user interface.  When I used Bazaar Explorer to
create a new branch from lp:Leo-Editor (the Trunk on LaunchPad), it
issued the following error:

KnitPackRepository('file:///C:/Leo/.bzr/repository/') is not
compatible with CHKInventoryRepository('http://bazaar.launchpad.net/
~leo-editor-team/leo-editor/trunk/.bzr/repository/') different rich-
root support

I then issued the following command from a command prompt (not from
within Bazaar Explorer):

  bzr upgrade --rich-root-pack

It created a backup of the local .bzr file and then restructured the
repository sub-directory.  I was then able to create a local branch
using the Bazaar Explorer's create Branch function.

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-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 pull from bzr

[TL]

When you installed bzr did you install the standalone package?  The
standalone package doesn't rely on your python installation.  If you
installed the Python 2.5 based version instead, you probably broke
bzr when you upgraded to Python 2.6.

You can reinstall a new version of bzr without losing the settings
associated with your local Leo repositories and branches.

Download the latest Windows version of bzr here:
http://wiki.bazaar.canonical.com/WindowsDownloads

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-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 pull from bzr

[TL]

I only use the Pageant program (Release 0.60).  I start it manually
after a computer restart, select the key file, and specify the
passphrase.

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-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: Vote for bugs you urgently want fixed

[TL]

The following undo functionality should be fixed:

Bug 498692: Undo deleted node renames current node's headline
Bug 498688: Undo back to last saved content still shows file as
modified (* in title)
Bug 362950: during body text undo selection goes nuts and view moves

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-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: geotag.py

[TL]

I'm intrigued but new to geotags and a little confused.  Will the
geotag in the subnode contain the geographic location of your
computer at the time the plugin is invoked based on its IP address or
is there some way to specify the geographic location you want
associated with the data in Leo?

Note: Perhaps, after my question, you have concluded that I'm not just
a little confused :-)

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-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: geotag.py

[TL]

Thanks.  It may come in handy someday but, as you pointed out, one
major benefit will come when you can invoke the plugin on a previously
tagged node and have the location displayed on the google map.

I also think users will want some way to keep the geotag from
affecting the content written by Leo.  For example, if the node's file
type has a defined comment delimiter then the geotag could be stored
as a comment.  Another possibility is to put the geotag under an
@ignore node.  Making it configurable should keep everyone happy.
For example, create a geotag_store_as_comment and a
geotag_store_under_ignore_node Leo configuration variables that can
be set to True or False.

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-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: Producing Latex documents from Leo

[TL]

 A. As with any @file node, saving a Leo outline will write the file
 if any part of the outline is dirty.  In effect, Leo automatically
 performs the rst3 command in such situations.

This feature has crossed my mind as I've been using rST to develop
HTML files.  My concern is that I don't necessarily want to have a new
HTML file created, which may have a last modified on date entry,
just because Leo has detected a change to a r
ST option or some other change that doesn't actually change the
visible HTML content.

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-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: Producing Latex documents from Leo

[TL]

Concerning the tangle and weave issues, can't I accomplish what is
needed by putting the documentation for a given module, function or
whatever in a node that is then cloned and included in the code and
the HTML/Latex document using a nodeName section name?

For example, if a function's description is placed in a node called
functionName() description then I can add it to the node containing
the python code as a comment by specifying:

   
   functionName() description
   

and in an @rst node containing the module's documentation under a
header by specifying:

   functionName
   ==
   functionName() description

Are you trying to achieve something more sophisticated?  If so, can
you provide an example showing the code and documentation files you
want to generate and how that would be accomplished within Leo's
outline?

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-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: Producing Latex documents from Leo

[TL]

 I've used LaTeX quite a bit, but if I can I prefer to write in rst, ...

rST support within Leo used to be a plugin but is now a part of Leo's
core.  However, the documentation is still located in Chapter 14 of
Leo's User Guide (http://webpages.charter.net/edreamleo/
rstplugin3.html).  I use rST to create HTML files.  Maybe somebody
else can describe what needs to be done to output Latex files.

Note: The following text uses the code/compile analogy to describe the
use of rST.  I think it best reflects the operation being performed.
Others disagree.

The rST code (actually written in the docutils language) is placed
within a Leo node that has an @rst directive in the node's header.
For example: @rst MyLatexFile

The rST code will be stored inside the leo file.  If you prefer to
keep the code in a separate file then place the @rst node under a
@thin node.  For example:

   @thin MyLatexFile.tex
  @rst MyLatexFile

The rST code is compiled into an HTML or Latex file by issuing the
command: c.rstCommands.rst3().  The easiest way to do this is to
create a button in Leo by placing the following node structure in the
Leo outline (or better yet, place it in the outline of your
myLeoSettings.leo file).  You can open up the myLeoSettings.leo file
from the Help menu.

   @settings
  @button rst3

Place the c.rstCommands.rst3() text (without the quotes) in the body
of the @button rst3 node.  Save the myLeoSettings.leo file and re-
open your leo file and you should see the button.  Select the @rst
node that you want to compile and select the rst3 button.  This
will place the output file in a directory defined by rST's
default_path option.

The rst options are defined in the body of the @rst MyLatexFile node
or you can put them in an ancestor node.  See Chapter 14 of the User
Guide for a list of the options.

@ @rst-options
code_mode=False
show_doc_parts_in_rst_mode = False
generate_rst=True
show_organizer_nodes=False
show_headlines=False
show_leo_directives=True
write_intermediate_file = False
verbose=True
@c

I hope this helps to get you going.  Don't hesitate to ask more
questions.

Welcome to Leo,
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-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: Vim mode issues

[TL]

Hello Paul,

Welcome to Vim emulation.  Unfortunately, I developed the Vim
emulation when Leo was using the Tk user interface.  You're comments
suggest that your running Leo with new Qt user interface (see some
problems I reported in the post:
http://groups.google.com/group/leo-editor/browse_frm/thread/9a5a40207abb162f).

The Vim emulation was implemented using Leo's key binding commands.
Unfortunately, I don't know the Qt package at all and only a little
bit of Leo's internal architecture.  I'm still hoping that one of the
Leo/Qt experts will volunteer to work on this area of the Qt
integration.

In the mean time, you can switch to using Leo with the Tk user
interface by adding the --gui=tk parameter when calling Leo (without
the quotes).  The Tk interface looks great on computers running
Windows.  I've heard it doesn't look so good on other platforms.  Give
it a try.

The Key+O indicates that the letter O should be pressed (without
pressing the Ctrl or Alt key).

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-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: quickmove.py updated

[TL]

Sorry to have to repeat myself but

Nice additions to the plugin.

Now would be a good time to add the place any undocumented plugin
here plugin to chapter 12 of the User Guide. :-)

TL

On Dec 7, 11:50 am, Terry Brown terry_n_br...@yahoo.com wrote:
 The quickmove.py plugin allows you to select a node and create a button
 which will move other nodes to this node.

 E.g. tidying up your todo list you select the Done node, click
 Move to first child button, and then click the new button to-done
 to move other nodes to the first child position of the Done node.

 New in this update:

   The Move menu is now also accessible in the context menu.

   There are now six types of movement:
     Move to first child
     Move to last child
     Copy to first child  *new*
     Copy to last child   *new*
     Clone to first child
     Clone to last child

   The menu items have moved from the Outline menu to the Move submenu
   of the Outline menu.

 Cheers -Terry

--

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: quickmove.py updated

[TL]

Sorry to repeat myself but

Nice additions to the plugin.

Now would be a good time to add the place any undocumented plugin
here plugin to chapter 12 of the User Guide. :-)

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-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: active_path rumination

[TL]

Nice additions to the plugin.

Now would be a good time to add the active_path plugin to chapter 12
of the User Guide.

--

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: pythonw does not terminate on exiting leo

[TL]

 I use the sourceforge app Console ...

Thanks for the recommendation.  I'll never go back.

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-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: pythonw does not terminate on exiting leo

[TL]

I launch my Leo project files by double-clicking on a .leo file in
explorer that launches the following batch file that has been
associated to the .leo extension.

Some things to note:

 - A DOS command window is left open but can be immediately closed
manually without effecting the launching of the Leo file.

 - I use a separate batch file to set which local Leo branch I'm
using.  If you always use Leo's Trunk branch then just change the
set /p Leo_Branch=  C:\Leo\Leo_Branch.txt line to set
Leo_Branch=Trunk

 - The set EDITOR=C:\Program Files\vim\vim72\gvim command defines
an environment variable used by Leo to launch an external editor.
Setting it in the batch file restricts its scope to the Leo file.  It
could be removed from this batch file and specified as a system wide
environment variable at the risk (low) that some other program may
also be checking for it.

 - The last line of the batch file contains the following code to
redirect Leo's runtime messages to a log file:
C:\Leo\Leo_%~n1_%random%.log 21
   The %~n1 embeds the name of the Leo project file without the
extension in the name of the log file.
   The %random% embeds a random number in the log file name to insure
each instance of Leo has its own log file.

Regards,
TL

Batch file:
---
rem Turn of the echoing of each command to the DOS window
@echo off

rem Get the local Leo branch to use (Leo_Branch.txt usually contains
Trunk)
set /p Leo_Branch=  C:\Leo\Leo_Branch.txt

rem Indicate which Leo branch were using (A reminder when opening a
Leo file)
echo Leo branch: %Leo_Branch%

rem Select the local Leo branch
cd c:\Leo\%Leo_Branch%

rem Select the EDITOR used by contextmenu.py (Qt gui)
set EDITOR=C:\Program Files\vim\vim72\gvim

rem Use Tk gui (comment out the next line to use the Qt gui)
set UseTK=--gui=tk

rem Launch Leo
cmd /c Pythonw leo\core\runLeo.py %1 %UseTK%  C:\Leo\Leo_%~n1_%random
%.log 21

--

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: rst with linked style sheets

[TL]

This problem was fixed.  See the following post:

http://groups.google.com/group/leo-editor/browse_frm/thread/8a06c3d4533467bb

--

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: @script nodes re-enabled

[TL]

A search for @script in the on-line User Guide and FAQ did not find
anything.  Is there any documentation on this directive?

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-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: file not found error when launching the vim plugin in the newest version

[TL]

 So now Leo depends upon the executable being in the user's search PATH

I'm running the latest revision (rev 2480) without my gvim.exe program
in the Windows' PATH environment variable.  Lexo finds the gvim.exe
file using the full path defined in the EDITOR environment
variable.  For example:

   set EDITOR=C:\Program Files\vim72\gvim

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-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=.

Re: is the following appropriate for this group?

[TL]

Fixed the problem reported in post:

http://groups.google.com/group/leo-editor/browse_frm/thread/bfb3bd971af1a9c8#

Thanks,
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-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=.

Re: Wave invites available

[TL]

I'd like to follow/contribute to the Leo waves.

e-mail: TL at TLTooLs (dot net)

Thanks,
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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Pygments vs. SilverCity

[TL]

 I am curios what do you think about replacing support for SilverCity with 
 Pygments

I replaced SilverCity with my own stylesheet by using rst's
stylesheet_path and stylesheet_name options (see Chapter 14 of the
user guide).

Note: Stylesheets are embedded in the HTML by default but you can set
the stylesheet_embed option to False to have the HTML file link to an
external stylesheet

Here is the current user guide content (the stylesheet_embed related
text will not be visible on the web based user guide until it is next
published):

stylesheet_name (default: 'default.css')
The name of the stylesheet passed to docutils.

stylesheet_path (default: '')
The directory containing the stylesheet passed to docutils.

:Note:
If the stylesheet_embed option is True, specify a path
relative
to the location of the Leo file.  If the stylesheet_embed
option is
False, specify a path relative to the location of the HTML
file.


stylesheet_embed (default: True)
True: The content of the stylesheet file will be embedded in the
HTML file.
False: The HTML file will link to an external stylesheet file.

Regards,
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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Edit with VIM: Inherit modeline

[TL]

 One thing I miss and can't figure out is how to inherit a modeline when I edit
 child nodes.

I have the same issue.  By definition, modelines must exist as
directives within the file.  Leo has no mechanism for appending lines
when the file is exported to an external editor and then removing them
when the file is imported back into Leo.

My solution is to use AutoBufRead as you have done or to create
plugins for each file extension that I want to run some custom Vim
code.  For example, if the file extension is .abc, place a vim.abc
file with the commands in the vimfiles/ftplugins directory.

This only works if the sub-nodes are exported to Vim with the
extension of the parent node appended to the temporary file.  Is that
occurring?

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

rst now supports linked stylesheets

[TL]

Support for generating HTML files from @rst nodes with a link to an
external stylesheet instead of having the stylesheet embedded in the
HTML file has been checked into the Trunk (revision 2471).

Edward, please verify that your latest changes in leoDocs.py were not
overwritten.  Also, can you publish Chapter 14 of the User Guide to
the Web.

The rst Options section in chapter 14 of the User Guide has been
updated with the following changes:

stylesheet_path (default: '')
The directory containing the stylesheet passed to docutils.

:Note:
If the stylesheet_embed option is True, specify a path
relative
to the location of the Leo file.  If the stylesheet_embed
option is
False, specify a path relative to the location of the HTML
file.

stylesheet_embed (default: True)
True: The content of the stylesheet file will be embedded in the
HTML file.
False: The HTML file will link to an external stylesheet file.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: rst with linked style sheets

[TL]

 The recommended definition of the rst3 button is now simply::

     c.rstCommands.rst3()

This is the rst3 button definition that I have been using.

 The new definition uses the core code in leoRst.py rather than
 the old rst3 plugin.

Yes, I have switched over to using the core code.

 The simple fix would be to use this in your myLeoSettings.leo.

I agree.  Unfortunately, when I move the rst3 button from the
project.leo file to the myLeoSettings.leo file, I get the following
error when I press the button:

exception executing script
  File C:\Documents and Settings\TL\.leo\scriptFile.py, line 3
.. include:: C:\_Proj\Head.rst
^
SyntaxError: invalid syntax

  line 2: #...@+node:@rst index.htm
* line 3: .. include:: C:\_Proj\Head.rst
  line 4:
  line 5: .. |Header| replace:: Overview

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

rst compile problem

[TL]

 I try to compile an @rst node with the rst3 plugin.

The problem also occurs with the rst implementation in the core.

Is anyone else having problems compiling an @rst node with the latest
Leo revision?

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Qt key mapping problem

[TL]

Help. I'm trying to switch from Tk to the Qt GUI.  Some of the key
mappings set in the Vim emulator don't work in the Qt GUI.  It appears
that the key is not being mapped and not a problem with the function
it calls.  Is it possible that the Qt GUI is capturing those key
events?  Some of the keys affected are the tab and the : keys.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: rst with linked style sheets

[TL]

 Does anyone have a solution ...

I implemented support for a new stylesheet_embed option that, when
set to False, will create a link to an external .css file instead of
embedding it in the HTML file.

I want to check it in but when I updated to the latest Leo revision, I
get the following error when I try to compile an @rst node with the
rst3 plugin.  Note that line 2 is using a # to start a comment line
even though a @language rst directive exists in a parent node.
There is no problem with revision 2441 dated 10/10/09.  Any ideas?

exception executing script
  File C:\Documents and Settings\TL\.leo\scriptFile.py, line 3
.. include:: C:\_Proj\Head.rst
^
SyntaxError: invalid syntax

  line 2: #...@+node:@rst index.htm
* line 3: .. include:: C:\_Proj\Head.rst
  line 4:
  line 5: .. |Header| replace:: Overview

--~--~-~--~~~---~--~~
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: Qt key mapping problem

[TL]

 You can start tracing it from leoQtEventFilter.eventFilter

Can you explain how to use this.

Also, what would the Qt pane be doing with these key presses when it
is in command mode?

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

rst with linked style sheets

[TL]

Does anyone have a solution in Leo for generating html from @rst nodes
that links to an external style sheet instead of embedding the style
sheet in the html file?

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: On rich text editing prototype

[TL]

 May I assume that the interest in the feature waned when the
 prototype is ready? Never fails... ;-).

I don't understand why someone who is interested in creating/viewing/
writing Rich-Text in Leo wants to see HTML code in the node's body
pane.

I want the node's body pane to show Rich-Text and allow me to edit it
with a simple WYSIWYG editor.  Leo would internally associate the Rich-
Text source as the node's text enabling it to easily read and write
Rich-Text files.

This would emulate the KeyNote program's approach, the basis for
Edward's initial ah-ha moment.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: 4.7 beta 1(Linux): edit in file extension?

[TL]

 Are you sure, if the @language is not supported? Perhaps this is a
 bug with c.openWith.

The mod_tempfname.py plugin also exists which overrides the openWith
plugin's code for generating the temporary file's directory and file
extension.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: On rich text editing prototype

[TL]

 I don't think that's too useful either. My idea would be to move the
 widget to the body pane eventually (from separate stickynote window)
 and hide the html.

Can you clarify what you mean by hide the html .  Microsoft's Rich-
Text file format is not html.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: site local plugins folder

[TL]

 Doh - never mind, I see now you were suggesting using this feature
 as a solution, not suggesting the addition of this feature.

After rereading my post it's clear that I wasn't clear.

We have already defined myLeoSettings.leo as the method for users to
tailor the plugins.  I'd rather not create another, alternate, method
for doing it.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Improving Leo's body pane

[TL]

It seems that we're discussing two separate enhancements:

The ability to render HTML in Leo if a user invokes a link or wants to
see the rendered results from an @rst node or a node containing raw
HTML code.

The ability to have Rich-Text nodes that, when selected, switch out
the existing text body pane with a Rich-Text body pane.

I doesn't appear that there is any interaction between these two
features.  Correct?

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Improving Leo's body pane

[TL]

 For example, we can imagine 'Source' and 'HTML' and 'rST' tabs.

What would the 'rST' tab have?  The rST code or the rST output (HTML)?
I would expect that I could keep my rST code in the the same outline
as the rest of my project (code and documentation kept together).

If the 'HTML' and 'rST' tabs are both showing rendered results, is it
necessary to have both tabs?  Why not just have a 'Rendered' tab that
renders the current node in the 'Source' tab based on the contents of
the node.

I'm also concerned about the usefulness of an HTML tab to show
rendered rST.  The HTML output usually requires a much wider pane than
the 80 character wide body pane I used to show the code.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Improving Leo's body pane

[TL]

KeyNote provides the ability to dump it's outline as a Rich-Text
formatted file.  I think it would be useful to have something similar
in Leo.

As a developer of a project, I might have a Design, To do, Open
issues, or other similar type sub-branch in the Leo outline that
I would want to printout for review with other team members.  The sub-
nodes could be text only or could contain Rich-Text.

The KeyNote code is available as a resource for how to combine nodes
and sub-nodes.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Improving Leo's body pane

[TL]

 The problem with full blown rich text support is only about how it
 integrates with rest of leo, and whether it will complicate / slow
 down the usual plain text code paths. The ui part is of course easy.

By full blown rich text support are you referring to nodes that read
and write Rich-Text formatted files directly?  These type of nodes
would show the rich-text in the 'Source' tab and allow users to bold,
color, and apply other types of rich-text formatting directly in the
body pane.  They would also allow a copy/paste from a web page in a
browser into the body pane, retaining the formatting.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Embedding section contents in rst3 trees

[TL]

I added a comment to the following comment to the bug report:

In addition to padding the sentinels with a blank line above and
below, you will also need to add a .. line between the last sentinel
and the trailing blank line to handle the case when subsequent lines
are indented.

Example:

blank line added by Leo
.. @-node:TL.20090712200026.2889:ABC*/
.. @+node:TL.20090723061608.2841:XYZ*/
..
blank line added by Leo
  User's text or rst directive
--~--~-~--~~~---~--~~
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: Scrolling commands - what should they do?

[TL]

It appears that there is no interest in correcting the scrolling
functions in Leo.

Past posts have talked about the desire for mouse-less editing within
Leo.  Key mappings exist in the Qt GUI to scroll the node's text but
they don't more the cursor.  How are the mouse-less users moving to
new locations within the body pane to edit text?

My understand is that scrolling has two purposes:

1. To continue editing the current line while adjusting the location
of that line within the body pane to view neighboring lines.

2. To access a different location within the buffer and edit at that
location.

Both are achieved by keeping the cursor at the current line as long as
the current line is visible.  When the line is no longer visible
change the current line to one of the visible lines.  Leo supports the
first use but not the second.  Currently, the only way to perform the
second use is to mouse-click on the new line to edit.  Correct?

A third purpose also exists:

3. To access a different location within a buffer, view/cut/copy some
text, and return back to the old location to continue editing.

My method for performing this when scrolling changes the current line
to keep the cursor visible is to mark the current line (Leo's point-to-
register command), scrolling to the location to view/cut/copy, and
then returning to the marked line (Leo's jump-to-register command) to
continue editing.

What other solutions exist?

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Scrolling commands - what should they do?

[TL]

Your correct about the use of cursor keys, pgup/pgdn, home, end.

Using them is better than the mouse but you're still moving your hands
off the keyboard's home position and taking your eye's off the
screen (at least I have to).  I prefer using A-Z (in Vim's command
mode) or their Ctrl and Alt key variations.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Scrolling commands - what should they do?

[TL]

 I have a great interest in anything that helps compatibility with vim or 
 emacs.

I didn't see this as a vim or emacs issue but I guess your right.  At
the moment, there doesn't seem to be anyone interested in mapping keys
to their personal preference or to emulate other editors.

 Have you filed a bug about this?  That would help us all track this issue.

At the moment, I'm just trying to get consensus on what the scrolling
should do.  Until we achieve that, there are no requirements defined
and, therefore, no bug to report.  That said, I could submit a change
request.  Is there a method to do that besides this forum?

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Rev 2432 - Crash on startup with Tk GUI

[TL]

I just updated my local Trunk branch to the latest trunk (rev 2432)

I get the following error during Leo startup running the Tk GUI on
WinXP:

Traceback (most recent call last):
  File leo\core\runLeo.py, line 650, in module
run()
  File leo\core\runLeo.py, line 95, in run
ok = doPostPluginsInit(args,fn,relFn,script)
  File leo\core\runLeo.py, line 365, in doPostPluginsInit
c,frame = createFrame(fileName,relativeFileName,script)
  File leo\core\runLeo.py, line 393, in createFrame
ok, frame = g.openWithFileName(relativeFileName or fileName,None)
  File C:\_Proj\Leo\trunk\leo\core\leoGlobals.py, line 2796, in
openWithFileName
ok = g.handleOpenHooks(c,old_c,gui,fn,f,readAtFileNodesFlag)
  File C:\_Proj\Leo\trunk\leo\core\leoGlobals.py, line 2859, in
handleOpenHooks
readAtFileNodesFlag=readAtFileNodesFlag) # closes file.
  File C:\_Proj\Leo\trunk\leo\core\leoFileCommands.py, line 899, in
open
silent=silent)
  File C:\_Proj\Leo\trunk\leo\core\leoFileCommands.py, line 792, in
getLeoFile
c.redraw()
  File C:\_Proj\Leo\trunk\leo\core\leoCommands.py, line 6476, in
redraw
c.frame.tree.redraw(p)
  File C:\_Proj\Leo\trunk\leo\plugins\tkGui.py, line 7296, in
redraw_now
self.redrawHelper(scroll=scroll,forceDraw=forceDraw)
  File C:\_Proj\Leo\trunk\leo\plugins\tkGui.py, line 7321, in
redrawHelper
self.drawTopTree()
  File C:\_Proj\Leo\trunk\leo\plugins\tkGui.py, line 7714, in
drawTopTree
self.drawTree(p,self.root_left,self.root_top,
0,0,hoistFlag=hoistFlag)
  File C:\_Proj\Leo\trunk\leo\plugins\tkGui.py, line 7742, in
drawTree
h,indent = self.drawNode(const_p,x,y)
  File C:\_Proj\Leo\trunk\leo\plugins\tkGui.py, line 7483, in
drawNode
return self.force_draw_node(p,x,y)
  File C:\_Proj\Leo\trunk\leo\plugins\tkGui.py, line 7492, in
force_draw_node
h2,w2 = self.drawUserIcons(p,beforeBox,x,y)
  File C:\_Proj\Leo\trunk\leo\plugins\tkGui.py, line 7547, in
drawUserIcons
h,w = 0,0 ; t = p.v.t
AttributeError: 'vnode' object has no attribute 't'

--~--~-~--~~~---~--~~
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: Rev 2432 - Crash on startup with Tk GUI

[TL]

Addtional info:
   Trunk rev 2420 works (was the current trunk on 10/2/09)
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Vim emulation - update

[TL]

Rev 2447 of the Trunk has restored the Scroll functionality in the Tk
GUI (still doesn't actually scroll [see previous post]) and updates
the Vim emulation to use it.  See the Vim History node in the
leoSettings.leo file for a list of the changes.

Let me know if there are problems/questions/suggestions.

Regards,
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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Rev 2432 - Crash on startup with Tk GUI

[TL]

 The fix is on the trunk at rev 2440.  All unit tests pass with tk enabled.

Thanks for the quick fix.  Very much appreciated.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Scrolling commands - what should they do?

[TL]

In a previous thread I indicated that scrolling was broken in Vim.
Actually, scrolling is no longer working within the body pane when
using the Tk GUI.  This was removed when the Qt support was added.
I've restored the code in a local branch and noticed that it doesn't
actually to a scroll.  Here's what I've found.

Tk:
Moves the cursor up/down the specified number of lines in the buffer,
scrolling the buffer if necessary to display the current line.

Qt:
Scrolls the buffer up/down the number of lines specified, maintaining
the same current line which may no longer be visible.

Vim:
Scrolls the buffer up/down the specified number of lines keeping the
cursor on the same line unless the line is no longer visible.  If the
line is no longer visible it changes the current line to the top or
bottom visible line.

I think Vim has the best approach.  Any other opinions?

Note: I tried using the w.scrollLines(n) function defined in
leoFrame.py to improve the scrolling in the Tk GUI but I get the
following error:

AttributeError: leoTkTextWidget instance has no attribute 'scrollLines'
--~--~-~--~~~---~--~~
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: More leoID changes

[TL]

  BTW, I don't see a point with dot in front of .leoID.txt filename
  anymore, as it's already in a hidden ~/.leo directory.

 True, but it doesn't seem worthwhile to change the name: we would still have
 to check for the old name if the new name wasn't found.

I don't know if this is a factor in the decision but it is difficult
(maybe impossible) to create a new file or rename an existing file to
a filename that starts with a period in the Windows File Explorer.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Embedding section contents in rst3 trees

[TL]

 Note that @thin nodes can't create valid rst unless you manually pad
 the beginning and end of every subnode with empty lines.

or the line containing the include directive can have a blank line
before and after 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: Embedding section contents in rst3 trees

[TL]

 Maybe there's a way to write a plugin that would get the best of both
 worlds?

It would be nice.

In the mean time, you can do something like this:

|
+ @rst mainfile.rst
   |
   + @thin first_include_file.inc
   |
   + @thin second_include_file.inc

You still have to use rST's include directive but you get the
hierarchy and can edit the include files in Leo.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Embedding section contents in rst3 trees

[TL]

I think I had the same problems.  My rST code uses the .. include:
full path to insert similar code into may rST files (HTML header
and footer code).  Unfortunately, the path to included file must be a
full path and not a path relative to the Leo file or, better yet, a
path derived from the @path directives in the parent nodes.

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 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 tried KeyNote?

[TL]

 The vim emulation maps the h,j,k,l keys to select the parent, next
 sibling, previous sibling, and the first child of the selected node.

Correction:
The vim emulation key bindings use the Ctrl-h,j,k,l as the primary
means to select a neighboring node from both the tree pane and the
body pane.  The j and k keys are also mapped to select the next and
previous nodes when in the focus is in the tree pane.  The h and l
keys are mapped to the vi/vim commands to move the cursor to the
previous and  next character.

--~--~-~--~~~---~--~~
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 tried KeyNote?

[TL]

I would also recommend key bindings to do a search and a search and
replace (or my preference: a replace and then search) command.  I also
like having these type of search commands automatically define the
scope of the search.  If the search command is issued when the focus
is in the tree pane then the headlines and body text for the current
node and all child nodes are searched.  If the search command is
issued when the focus is in the body pane then only that body pane is
searched.

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 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 tried KeyNote?

[TL]

 I've also been thinking of providing vi-like tree movement/manipulation

Take a look at the tree manipulation key bindings used for the vim
emulation specified in the leoSettings.leo file under: @keys vim
bindings - @shortcuts - vi in outline pane.  The should give you a
good start.

 i would insert
Keep in mind that a node can be in one of three states: Grayed,
Command, and Insert.  The vim emulation has mapped different keys to
move between them.  You will want to do something similar if you want
to avoid mouse clicking.

 h edits headline...

Check out the vim emulation documentation in Leo's user guide for
additional headline editing ideas.  Also be aware when mapping keys to
Leo functions that some of Leo's editing functions don't work
correctly when the headline has focus (see the Vim Developer
Documentation node in leoSettings.leo)

 u,d,l,r moves nodes

The vim emulation maps the h,j,k,l keys to select the parent, next
sibling, previous sibling, and the first child of the selected node.

 where you's never need ctrl key when tree has focus

The ctrl-h,j,k,l keys aren't needed in the vim emulation but have been
mapped to the same select neighboring node functions as their
h,j,k,l counter parts.  This was done because the ctrl-h,j,k,l keys
are used in the body pane to switch to a neighboring node without
having to change focus to the tree pane.

Moving a node when using the vim emulator is done by mapping Alt-
h,j,k,l keys to move the selected node up a level, down one sibling,
up one sibling, and down a level.

A similar type of setup could be created if your going to use the
u,d,r,l keys.

Let me know if you have any questions.

Regards,
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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Vim broken - Scrolling up and down

[TL]

Sometime before June 21st the scroll-up and scroll-down commands were
replaced by scroll-up-page and scroll-down-page commands in the
leoEditCommands.py.  This broke the
key bindings defined in the Vim Emulation code.

Unfortunately, the following change doesn't work:
   scroll-up-page ! body = Ctrl-b
   scroll-down-page ! body = Ctrl-f

This didn't work either:
   scroll-up-page = Ctrl-b
   scroll-down-page = Ctrl-f

It appears that the scroll-up-page and scroll-down-page only work if
mapped to the keys Next and Prior.  What are these keys?
Even selecting the  functions from the Cmds-Scrolling... menu stops
working if the key mapping is changed.

Note: This is the second time the Vim emulation has broken due to
changes to Leo's edit commands being made without adequate
investigation of side effects.

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 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 different caching bug

[TL]

 If you have
foo.txt:
   A -- B -- C
mycode.py:
   D -- B -- E

How can 'C' appear under the one 'B' clone without also appearing
under the other 'B' clone?  If I place a node under a cloned node it
also appears under all of the cloned node's clones.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

rst script examples outdated

[TL]

The rst3 plugin is required to use the script examples given in the
@@button rst example in the leoSettings.leo file and in Chapter 14
of the users guide (shown below).  They should be updated to utilize
the new rST functionality in Leo's core.

Until that is done, can someone post a working @button rst script
that doesn't require the rst3 plugin?  I would like to test the rST
implementation in Leo's core.

Script in @@button rst example in the leoSettings.leo file:
|   import leoPlugins
|   rst3 = leoPlugins.getPluginModule('rst3')
|   if rst3:
|   controller = rst3.controllers.get(c)
|   if controller:
|   controller.processTopTree(p)
|   else:
|   rst3 = leoPlugins.loadOnePlugin('rst3',verbose=True)
|   if rst3:
|   g.es('rst3 loaded')
|   rst3.onCreate('tag',{'c':c})
|   else:
|   # Ask to be removed.
|   g.app.scriptDict['removeMe'] = True

Script in Chapter 14 of the users guide:
|   import leo.core.leoPlugins as leoPlugins
|   rst3 = leoPlugins.getPluginModule('rst3')
|   if rst3:
|   controller = rst3.controllers.get(c)
|   if controller:
|   p,s = controller.writeNodeToString(ext='.html')
|   print '*' * 40,p
|   print s

--~--~-~--~~~---~--~~
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(s) request: Expand reST output types

[TL]

 I have a leo-rst-inkscape mashup which lets you write
 slides quickly and easily using leo / rst, but uses
 inkscape to render pretty backgrounds and master template
 stuff, and also allows per slide inkscape arbitrary svg
 for diagrams etc.

 I'll try and get the current version up on the web
 somewhere today.

Just a reminder.


--~--~-~--~~~---~--~~
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: Path changed for @thin

[TL]

If you want to save a file into multiple directories try using the
Multifile.py plugin.  I haven't used it but it is designed to save the
same @thin node into multiple directories.  See the plugin
documentations at:

http://webpages.charter.net/edreamleo/plugins.html#multifile-py

If you give it a try, let us know if it works.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Cool hack: detach body editor

[TL]

I use the external Vim editor differently.  Working on an aspect of my
project often requires changes to 3 or more nodes located in different
areas of the outline.  By exporting each of them to tabs within Vim I
get the advantage of both the better Vi emulation and easier switching
between the nodes I'm interested in (the same concept as Edward has
for using Leo's clones to gather nodes together for a given task).

I don't want the content of the current Vim tab changing when I change
Leo's current node.  I often have Leo pointing to a node that I'm not
editing.  For example, when using the rst3 plugin to create html
files, Leo's current node is the .rst node that needs to be compiled
while Vim's tabs contain the node's being edited.

That said, I could see situations where it would be nice to have a tab
in Vim that reflects the current Leo node with the ability to move to
next previous node from within Vim.  Perhaps we could implement the
concept of exporting a Leo node to a node buffer in Vim that would
support this while still supporting Vim buffers that map to a specific
node.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: ok to retire the rst3 plugin?

[TL]

When I disable the rst3 plugin I get the following messages in the Log
tabcard when I select the rst3 button for the first time:

   loaded plugin: rst3 mainloop.__cal__. atSetButtonCallback.there's
more
   rst3 loaded

When I select the rst3 button again, it process the node.

I assume the button's script needs to be changed.  Here's what I'm
using:

import leo.core.leoPlugins as leoPlugins

rst3 = leoPlugins.getPluginModule('rst3')

if rst3:
controller = rst3.controllers.get(c)
if controller:
controller.processTopTree(p)
else:
rst3 = leoPlugins.loadOnePlugin('rst3',verbose=True)
if rst3:
g.es('rst3 loaded')
rst3.onCreate('tag',{'c':c})
else:
# Ask to be removed.
g.app.scriptDict['removeMe'] = True

--~--~-~--~~~---~--~~
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: Preset folder for images etc.

[TL]

 Is there anyway to declare this folder to a
 variable/directive or something, ...?

No, the rST standard doesn't support the definition of a base
directory for the .. image:: directive.  However, if you're creation
HTML, browsers support a path definition relative to the location of
the .htm file.  For example, you can specify
the following Leo option to store you HTML files in a specific
directory:

   default_path=C:\Projects\MyProject

and, if you're images are in C:\Project\MyProject\Images
subdirectory, you can use the rST directive such as:

   .. image:: Images\test.jpg

Regards,
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 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 navigate through the outline

[TL]

If you find that moving your hand over to the arrow keys is not much
better than using the mouse, consider using the ctrl and alt key
combinations.  For example, the h, j, k, and l keys are cursor
movement keys in the Vi/Vim editor.  Leo's Vi/Vim emulator maps ctrl-
h, -j, -k, and -l to move between nodes.  This works when the focus is
in either the outline or the body.  In addition, the Tab key is used
to toggle focus between the body and the outline.

If your not a Vi/Vim user and want to map other ctrl key (or alt key)
combinations, check out the code used in the vim emulator.  Changing
the key mapping is not difficult.

Regards,
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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Vim plugin not working on 4.6.1 final?

[TL]

 Could we disable the doubleclick functionality for vim.py?

My first reaction was no.  The double-click handler is designed to
allow multiple plugins to share the event; Each plugin deciding if it
should pass the event to the next plugin.  Using the nodeActions.py
and the vim.py allowed me to perform multiple actions on a double-
click depending on the type of node.  And, since I'm one of those
avid keyboarders, I mapped the double-click event to the `=` key
using the following:

   double-click-icon-box  ! body = equal

However, if the vim.py plugin no longer registers with the double-
click event, I can have the nodeActions.py plugin launch it as the
default action.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: Builtin rst3: How to invoke?

[TL]

 Check out LeoSettings.leo, and ...

It is better to not modify the leoSettings.leo file and, instead,
create or change your myLeoSettings.leo file to contain a copy of the
@button rst3 node under a @settings - @buttons node.  The
leoSettings.leo file exists to hold the default settings and may be
overwritten the next time you update Leo.  Users are expected to use a
local myLeoSettings.leo file to hold their user specific settings.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---

Re: @button clone-marked: easy way to create clones

[TL]

Thanks.  This will be useful.

While testing it, I noticed that the undo command does not undo the
creation of the clones.  It would be nice to support this if possible.

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 email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---