As a data point, '@settings -> @bool vim-mode = True' enables Vim-mode
with proper : handling for me, and I'm running on:
Leo 4.11 final, build 4f355e273b8d (branch: master), 2014-08-14 21:21:05
Python 2.7.3, PyQt version 4.8.4
Windows 7 AMD64 (build 6.1.7601) SP1
I didn't run with an empty config, though.
-->Jake
On 8/14/2014 8:10 PM, Steve Zatz 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.
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
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.
Steve
Results of print-settings
[D] allowclonedrags = True
[D] bodypanewraps = True
[D] bodytextfontfamily = Courier
[D] bodytextfontsize = 9
[D] bodytextfontslant = roman
[D] bodytextfontweight = normal
[D] colordirectivesinplaintext = True
[D] enabledragmessages = True
[D] headlinetextfontfamily = None
[D] headlinetextfontsize = 8
[D] headlinetextfontslant = roman
[D] headlinetextfontweight = normal
[D] ignoreblanklines = True
[D] initialhorizontalratio = 0.3
[D] initialhorizontalsecondaryratio = 0.5
[D] initialsplitorientation = vertical
[D] initialverticalratio = 0.5
[D] initialverticalsecondaryratio = 0.7
[D] initialwindowheight = 600
[D] initialwindowleft = 10
[D] initialwindowtop = 10
[D] initialwindowwidth = 800
[D] limitcount = 9
[D] logtextfontfamily = None
[D] logtextfontsize = 8
[D] logtextfontslant = roman
[D] logtextfontweight = normal
[D] outputdocchunks = True
[D] pagewidth = 132
[D] printmismatchinglines = True
[D] printtrailinglines = True
[D] searchbody = True
[D] splitbarcolor = LightSteelBlue2
[D] splitbarrelief = groove
[D] splitbarwidth = 7
[D] tabwidth = -4
[D] tangleoutputsheader = True
[D] targetlanguage = python
[D] underlineundefinedsectionnames = True
[F] vimmode = True
[D] wholeword = True
legend:
leoSettings.leo
[D] default settings
[F] loaded .leo File
[M] myLeoSettings.leo
On Thu, Aug 14, 2014 at 4:37 PM, Edward K. Ream <edream...@gmail.com
<mailto:edream...@gmail.com>> wrote:
On Thu, Aug 14, 2014 at 2:56 PM, Edward K. Ream
<edream...@gmail.com <mailto:edream...@gmail.com>> wrote:
> On Thu, Aug 14, 2014 at 11:41 AM, Steve Zatz <slz...@gmail.com
<mailto:slz...@gmail.com>> wrote:
>> As below the following files are being read but the only file
with any
>> settings is myLeoSettings.leo and it consists of one @settings
with @ bool
>> vim-mode = True
>
> Thanks for your persistence. I'll try a similar setup and see
what happens...
I disabled leoSettings.leo and myLeoSettings.leo by changing their
names.
When I tried to load ekr.leo, Leo crashed trying to load an enchant
dict. After correcting that (upped using git) ekr.leo loaded. I then
did the following:
1. disabled the normal @settings node by renaming it.
2. I created another @settings node containing just @bool vim-mode
= True.
3. I restarted Leo and loaded ekr.leo.
As you say, Leo looks like a dos app :-)
4. I then clicked in the minibuffer area (no key bindings!) and
executed the print-settings command by typing "print-settings<return>"
I selected the text with the mouse, then clicked the minibuffer area
again and did copy-text. I then pasted the text here. Here is what I
got::
[D] allowclonedrags = True
[D] bodypanewraps = True
[D] bodytextfontfamily = Courier
[D] bodytextfontsize = 9
[D] bodytextfontslant = roman
[D] bodytextfontweight = normal
[D] colordirectivesinplaintext = True
[D] enabledragmessages = True
[D] headlinetextfontfamily = None
[D] headlinetextfontsize = 8
[D] headlinetextfontslant = roman
[D] headlinetextfontweight = normal
[D] ignoreblanklines = True
[D] initialhorizontalratio = 0.3
[D] initialhorizontalsecondaryratio = 0.5
[D] initialsplitorientation = vertical
[D] initialverticalratio = 0.5
[D] initialverticalsecondaryratio = 0.7
[D] initialwindowheight = 600
[D] initialwindowleft = 10
[D] initialwindowtop = 10
[D] initialwindowwidth = 800
[D] limitcount = 9
[D] logtextfontfamily = None
[D] logtextfontsize = 8
[D] logtextfontslant = roman
[D] logtextfontweight = normal
[D] outputdocchunks = True
[D] pagewidth = 132
[D] printmismatchinglines = True
[D] printtrailinglines = True
[D] searchbody = True
[D] splitbarcolor = LightSteelBlue2
[D] splitbarrelief = groove
[D] splitbarwidth = 7
[D] tabwidth = -4
[D] tangleoutputsheader = True
[D] targetlanguage = python
[D] underlineundefinedsectionnames = True
[F] vimmode = True
[D] wholeword = True
legend:
leoSettings.leo
[D] default settings
[F] loaded .leo File
[M] myLeoSettings.leo
This shows that only default settings are in effect, except that
ekr.leo sets vim-mode to True.
With these settings, (drum roll please), colon *does* work as
expected.
This shows, I think, that *only* the @bool vim-mode setting is
necessary to use vim mode.
===== Conclusion
I recommend that you do the following:
1. Get rev a69585e... from git. This fixes a startup problem when no
settings exist.
2. Follow exactly the steps that I have just taken and report what
colon does in vim mode.
Thanks.
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 leo-editor+unsubscr...@googlegroups.com
<mailto:leo-editor%2bunsubscr...@googlegroups.com>.
To post to this group, send email to leo-editor@googlegroups.com
<mailto:leo-editor@googlegroups.com>.
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
--
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 leo-editor+unsubscr...@googlegroups.com
<mailto:leo-editor+unsubscr...@googlegroups.com>.
To post to this group, send email to leo-editor@googlegroups.com
<mailto:leo-editor@googlegroups.com>.
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
--
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
