I must warn you when you reach level 2, you need to buy a license =(
So I checked for a while and would recommend those:
Vim casts:
http://vimcasts.org/
Learning and memorizing shortcuts:
https://www.shortcutfoo.com/app/tutorial/vim
More resources here:
http://stackoverflow.com/questions/757921
On Fri, Aug 8, 2014 at 12:19 PM, Edward K. Ream wrote:
> On Fri, Aug 8, 2014 at 9:36 AM, Edward K. Ream wrote:
>
>> vim-training mode will disable the operation of all arrow keys, [except]
>> Alt-arrow keys
>
> Recent revs implement vim-trainer. OMG, vim-trainer is *intense*.
> Here are some no
On Fri, Aug 8, 2014 at 9:36 AM, Edward K. Ream wrote:
> vim-training mode will disable the operation of all arrow keys, [except]
> Alt-arrow keys
Recent revs implement vim-trainer. OMG, vim-trainer is *intense*.
Here are some notes:
1. vim-trainer *instantly* changed how I use vim mode. jj b
On Fri, Aug 8, 2014 at 11:46 AM, 'Terry Brown' via leo-editor
wrote:
>> I don't get the point of this link.
>
> It's a game you play with vim keystrokes, designed to make you vim
> proficient. It seemed relevant to your vim-trainer idea.
Thanks. vim-trainer could be called something similar.
On Fri, 8 Aug 2014 11:39:09 -0500
"Edward K. Ream" wrote:
> On Fri, Aug 8, 2014 at 9:56 AM, 'Terry Brown' via leo-editor
> wrote:
>
> > Fidel pointed this out on IRC
> > http://vim-adventures.com/
>
> I don't get the point of this link.
It's a game you play with vim keystrokes, designed to ma
On Fri, Aug 8, 2014 at 9:56 AM, 'Terry Brown' via leo-editor
wrote:
> Fidel pointed this out on IRC
> http://vim-adventures.com/
I don't get the point of this link.
EKR
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this g
On Friday, August 8, 2014 9:57:43 AM UTC-5, Dave Loyall wrote:
>
> Here are some words about Leo.
>
> https://hn.algolia.com/?q=leo-editor#!/all/forever/0/%22leo-editor%22
>
> You'll note that folks discussing Leo on HN fall into three camps.
>
I don't see any really negative remarks about Leo.
On Fri, Aug 8, 2014 at 9:55 AM, Edward K. Ream wrote:
>
> On Ubuntu I'm getting tracebacks at idle time when I type in the body
> pane after doing the livecode-show command.
Hmm. Not sure what happened :-) Things seem to be working for me
pretty much as I would expect.
EKR
--
You received t
well ill wait till "c." completes well then try to find out the difference,
but I really trust when the other thing is fixed this also will.
Thanks
On Fri, Aug 8, 2014 at 4:58 PM, 'Terry Brown' via leo-editor <
leo-editor@googlegroups.com> wrote:
> On Fri, 8 Aug 2014 09:39:42 -0500
> "Edward K.
On Fri, 8 Aug 2014 09:39:42 -0500
"Edward K. Ream" wrote:
> On Fri, Aug 8, 2014 at 8:06 AM, Fidel N wrote:
> > And when trying to complete "c.p." no autocompletion appears, and
> > this error pops up in the log pane:
>
> Not for me. I suspect this only happens when using the Qt-base
> auto-com
Here are some words about Leo.
https://hn.algolia.com/?q=leo-editor#!/all/forever/0/%22leo-editor%22
You'll note that folks discussing Leo on HN fall into three camps. (Well, can a
"camp" have a population of one?)
1. It's great!
2. It looks terrible, I'm done investigating.
3. It's terrible, ex
On Fri, 8 Aug 2014 07:36:48 -0700 (PDT)
"Edward K. Ream" wrote:
> One last hope appeared yesterday. I call it vim trainer mode.
Fidel pointed this out on IRC
http://vim-adventures.com/
Cheers -Terry
--
You received this message because you are subscribed to the Google Groups
"leo-editor" gr
On Wed, Aug 6, 2014 at 2:42 PM, 'Terry Brown' via leo-editor
wrote:
> Just pushed the livecode.py plugin, screenshot attached.
Very cool.
On Ubuntu I'm getting tracebacks at idle time when I type in the body
pane after doing the livecode-show command.
For example, I get the tracebacks continuou
On Fri, Aug 8, 2014 at 8:06 AM, Fidel N wrote:
> And when trying to complete "c.p." no autocompletion appears, and this error
> pops up in the log pane:
Not for me. I suspect this only happens when using the Qt-base
auto-completer widget.
EKR
--
You received this message because you are subsc
On Fri, Aug 8, 2014 at 8:02 AM, Fidel N wrote:
> Thanks for the fix, but I think it doesnt work yet:
>
> Doing "c." will lead to autocompleter still completing wrong.
> Options such as "p", "redraw", etc just dont appear.
> "baseescanner" still appears as an option.
I agree.
Edward
--
You rece
At present, I am far from loving using vim mode. I use it because I must:
it's the only way to shake down subtle bugs and to get the true feel for
the code.
I thought that using vim (for real) for a week or so might make me more
comfortable with it. Not yet.
True, some aspects of vim are bec
At present, vim-mode's top-level key handler, vc.do_key, passes *all* keys
back to Leo (k.masterKeyHandler) when focus is not in the body pane.
This is way too confusing: almost all vim bindings will mysteriously appear
to stop working if, say, focus is in the outline pane. This is likely the
On Fri, 8 Aug 2014 07:39:21 -0500
"Edward K. Ream" wrote:
> On Thu, Aug 7, 2014 at 9:02 AM, 'Terry Brown' via leo-editor
> wrote:
>
> > Phew :-} not me https://github.com/leo-editor/leo-editor/issues/40
>
> Rev d343dde... rolls back the code.
>
> I'm not happy with the old code, and the autoc
On Fri, 8 Aug 2014 07:39:21 -0500
"Edward K. Ream" wrote:
> On Thu, Aug 7, 2014 at 9:02 AM, 'Terry Brown' via leo-editor
> wrote:
>
> > Phew :-} not me https://github.com/leo-editor/leo-editor/issues/40
>
> Rev d343dde... rolls back the code.
>
> I'm not happy with the old code, and the autoc
And when trying to complete "c.p." no autocompletion appears, and this
error pops up in the log pane:
exception executing command
Traceback (most recent call last):
File "D:\leo-editor\leo\core\leoCommands.py", line 539, in doCommand
val = command(event)
File "D:\leo-editor\leo\core\leoK
Thanks for the fix, but I think it doesnt work yet:
Doing "c." will lead to autocompleter still completing wrong.
Options such as "p", "redraw", etc just dont appear.
"baseescanner" still appears as an option.
On Fri, Aug 8, 2014 at 2:39 PM, Edward K. Ream wrote:
> On Thu, Aug 7, 2014 at 9:02
On Fri, Aug 8, 2014 at 6:57 AM, Steve Zatz wrote:
> I may be doing something wrong but when I type a colon in normal mode
> nothing is happening. When I type :q, nothing happens except the log file
> prints "not ready vim_q".
:q works for me in Normal mode. The comma takes me to the minibuffer,
On Thu, Aug 7, 2014 at 9:02 AM, 'Terry Brown' via leo-editor
wrote:
> Phew :-} not me https://github.com/leo-editor/leo-editor/issues/40
Rev d343dde... rolls back the code.
I'm not happy with the old code, and the autocompleter still doesn't
seem to do a good job. For example, I expect c.frame
I may be doing something wrong but when I type a colon in normal mode
nothing is happening. When I type :q, nothing happens except the log file
prints "not ready vim_q".
Besides setting @bool vim-mode = True, do I need to do anything else?
Steve
On Thu, Aug 7, 2014 at 1:21 PM, Edward K. Ream
On Fri, Aug 8, 2014 at 2:15 AM, Ville M. Vainio wrote:
> I think there is also a setting to NOT store expanded state in .leo files.
Yes: @bool put_expansion_bits_in_leo_files = Files
And (for once ;-) the setting is where one might expect it:
leoSettings.leo#@settings-->Files & directories-->Le
On Thu, Aug 7, 2014 at 5:36 PM, David McNab wrote:
> What's been the general observation of Git and .leo files?
That has not been a problem only because of this general Leo work flow:
http://leoeditor.com/FAQ.html#how-should-i-use-leo-with-bzr-git-hg-svn-cvs
Edward
--
You received this messa
I think there is also a setting to NOT store expanded state in .leo files.
On Aug 6, 2014 8:56 PM, "Zoltan Benedek" wrote:
> Hi,
>
> I don't know whether is documented or not this idea, but I wanted to be
> sure, that is not lost.
>
> If your leo file is in source control management system (like
27 matches
Mail list logo
