On Thu, Aug 14, 2014 at 7:10 PM, Steve Zatz <[email protected]> wrote:
> I followed the directions although I wasn't sure what ekr.leo was so I just
> created a new test.leo and inserted the vim = true @ setting in that new
> file and then reloaded that file.  As before vim navigation and key
> sequences like dd work fine.  The print-settings result (see below)  looks
> just like your key bindings but alas no dice with regard to typing a colon.

Thanks for running this experiment!  As you say, ekr.leo is just a
test file.  You did exactly right by creating test.leo as you did.

> Another thought is whether the version of python, PyQt or Windows could be a 
> factor.  I am running on the following:
>
> Python 2.7.2, PyQt version 4.8.5
> Windows 7 AMD64 (build 6.1.7601) SP1

FYI, my machine is:

Python 2.7.2, PyQt version 4.7.3
Windows 7 AMD64 (build 6.1.7601) SP1

So there may be a PyQt issue. Keyboard issues are also possible.

> If I am the only one experiencing this problem (and apparently I am), I
> definitely think you should move on to other issues. I really appreciate the
> time you've spent on it.   I'll try some other machines/OS's and let you
> know if I discover anything.  Thanks again for trying to figure this out.

Yes, trying the code on other machines is a good strategy.

But it's important to understand what is going on.  For sure,
*something* strange is happening, and if it happening to you, it could
happen to others.  Including me ;-)

If you are willing, I would suggest enabling tracing in the following methods:

- LeoQtEventFilter.eventFilter in qtGui.py
- vc.do_key, in leoVim.py,
- k.masterKeyHandler in leoKeys.py.

To do this, open a leoPy.leo (a local copy of LeoPyRef.leo), and in
each method, change:

    trace = False and not g.app.unitTesting

to::

    trace = True and not g.app.unitTesting

Save leoPy.leo, rename leoSettings.leo and myLeoSettings.leo as before
so as to disable them, run your test.leo (in a windows console!) and
report what appears in the console when you type a colon.

Yes, this is a bit of work.  But it should be worthwhile. These traces
provide an thorough view of the machinations that Leo goes through
when handling key events.  There is a good chance that important clues
will appear.

Thanks for your help on this project.  Imo, it is important to solve
this problem, whatever it's ultimate cause.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to