I want I can use duplicated 20j commands. What do you think?

It would be great if you could completely disallow some keys (e.g. arrow keys) while allowing some other keys (e.g. hjkl) only once or twice.

As far as I can tell, if I want to allow hjkl for one or two presses then I also have to allow arrow keys for the one or two presses.

Whenever YCM is showing its autocomplete list, I can't just fast scrolling looking up modules that I want to use/explore. Here is what I meant by YCM autocomplete :

For this autocomplete, vim-hardtime will limit my scrolling movement for 1 second.
So can we disable whenever this autocomplete popup appears and enable vim-hardtime back when popup disappears?

Hello, such a great plugin over here, I'm trying to disable hardtime on the vimshell buffers but I can not make it to work, I've tried this with no success:

let g:hardtime_ignore_buffer_patterns = ["NERD.*", "*vimshell*"]
let g:hardtime_ignore_buffer_patterns = ["NERD.*", "vimshell"]
let g:hardtime_ignore_buffer_patterns = ["NERD.*", "vimshell*"]

On vim-shell buffer name appears as [vimshell] - default and filetype is vimshell.

Thanks in advance!

Are there any ways to temporarily disable this plugin, for casual browsing and reading code.

Or any recommended ways to do it?

With vim-hardtime enabled sometimes I see wield error messages like:

E109: Missing ':' after '?'
E15: Invalid expression: TryKey('j') ? 'TryKey('j') ? 'TryKey('j') ? 'TryKey('j') ? 'j' : TooSoon()' : TooSoon()' : TooSoon() : TooSoon()

If I disable vim-hardtime then this does not happen. I see this error come up more when working with splits than anything else.

It would be really nice if there was an option to allow h,j,k,l if it's after a motion.

For example. 3j or 5k should be entirely allowed. I use relative numbers so for me I use this method to navigate round a lot. Would it be possible to have an option to allow this?

Thanks!

It seems as though vim-hardtime is incompatibel with Snipmate. Snippets that contain for example ${1:var} won't execute correctly if ${1:var} is replaced with a word that starts with j, k, l or h.

the project has no license

This plugin introduces a map on the - key that conflicts with the invocation of vim-vinegar.

not sure what the reason of this map is but when looking at active mapings I saw the following:

in other words somehow vim-hardtime tries to wrap the - mapping but it never invokes vinegar.

There are some use cases when you are ready to move your cursor right after a keystroke but before the hard time timeout has expired.

While I've been using vim for a few years and even though I use b,e,etc. keys sometimes, most of the times I find myself using h,j,k,l to browse code.

Adding to the Readme what you should do instead of navigating using arrow keys would benefit some users.

Im a vim frecuent user and after a full day trying to use hardtime mode i start see changes ...

Hi,

Thank you very much for this plugin! It's exactly what I need to learn how to not rely so much on hjkl.

Does anyone know how one can get this working with [ideavim[(https://github.com/JetBrains/ideavim)?

Please feel free to close this if it doesn't fit here.

Hi,
I installed hardtime with Vundle, but nothing happen here:

Plugin 'takac/vim-hardtime' 

:bundleInstall

"hardtime
let g:list_of_normal_keys = ["h", "j", "k", "l", "-", "+", "<UP>", "<DOWN>", "<LEFT>", "<RIGHT>"]
let g:list_of_visual_keys = ["h", "j", "k", "l", "-", "+", "<UP>", "<DOWN>", "<LEFT>", "<RIGHT>"]
let g:list_of_insert_keys = ["<UP>", "<DOWN>", "<LEFT>", "<RIGHT>"]
"let g:list_of_disabled_keys = []
let g:hardtime_timeout = 2000 "2 sec
let g:hardtime_showmsg = 1

It would be nice if we could set the timeout to something like 500ms.

The plugin works when running starting nvim, provided you specify the file name.
Running the command

nvim test.txt

makes the plugin work as expected.
However, when running

nvim

by itself, the plugin doesn't initiate.
I have the plugin config set in ~/.config/nvim/init.vim

Running

:HardTimeOn

when in nvim enables the plugin. But it still doesn't enable itself on startup without a file name specified.

let g:hardtime_default_on = 1

is of course set

I agree in some cases repeating could be inefficient, and should be done with some advanced movements. But sometimes repeating could be faster than complex key sequences. For example, I normally set keyboard repeat rate to maximum, so it is not only easier, but also faster to hold j, than the key sequence 20j, to go down 20 lines. But of course jumping more lines it is generally better to instead use ctrl-f.

add a message to remind the user of a few helpful movement tips

If anyone wants a simple hardtime, try :nn jj <nop> like in https://stackoverflow.com/a/23489147. I hardtimed b and w in my vimrc

I'm using tpope's fugitive. - is used to (un)stage a file to git's index.
When Hardtime is enabled it overrides this shortcut (visual and normal modes) so I can't do the mentioned action anymore.

I added .git/index (the result from :echo bufname('%') to:

let g:hardtime_ignore_buffer_patterns = [ "NERD.*", ".git/index" ]

restarted vim, but didn't work. I've run :verbose map - and it showed that - mapping was last set by hardtime, still.

Disabling the plugin & restarting vim put the behaviour back to normal...

What should I do with this plugin if I want to go UP/DOWN?

1. easymotion to jump to the word.

2. Repeat 'W' times to next line
   or repeat 'E' times to prev' line.
   [ It's horrible ... ]

3. Search the word even the word is at EOL of next line.

4. ? I just using vim the wrong way.

I'd like the ability to disable hardtime while in a help buffer. Generally I find non-optimal patterns like holding down j to scroll within buffers that are mostly just text to be just fine.

I'm happy to code it up and submit a pull request. Do you have any preference on implementation?

We could add g:hardtime_ignore_help and s:IsIgnoreHelp() just like the quickfix counterparts, or combine the implementations of s:IsIgnoreQuickfix and call it something like s:IsIgnoreSystem

add documentation for vim-plug users

First of all: thank you for taking the time to write this plugin. It's cool that you want us to be better Vimmers 😄

I'd like to disable vim-hardtime when moving through the quickfix window. Is that possible? I tried using g:hardtime_ignore_buffer_patterns, but didn't worked.

If you have a macro that does an action and run it again, if the action is j or something else, it doesn't work. To reproduce:

qqjq to record a macro of going down a line, @q@@ to run the macro, then again. The second time you run the macro, nothing happens because HardTime is blocking you. I don't know if you can detect a macro being run though.

I'm using CamelCaseMotion with the following config:

NeoBundle 'bkad/CamelCaseMotion'
map <C-W> <Plug>CamelCaseMotion_w
map <C-B> <Plug>CamelCaseMotion_b
map <C-E> <Plug>CamelCaseMotion_e

NeoBundle 'takac/vim-hardtime'
let g:hardtime_default_on = 1
let g:list_of_normal_keys = ["w", "b", "e", "W", "B", "E",
      \ "<c-w>", "<c-b>", "<c-e>", "gj", "gk", "h", "j", "k", "l"]

For some reason specifically keys <C-e/b/w> do nothing when I press them while others work OK. Without vim-hardtime C-* keys work OK.

make all configuration lines copy and pasteable
for convenience

Hi, this plugin is great! Thanks for it.

But it would be cool to list some exceptions like NERDTree buffer. Imagine we have:

folderA
folderB

And the cursor is in folderA and we want to go to folderB and then open it, and then open the first file under it... You can see this quickly become annoying as in this case just navigating down is the quickest way...

When g:hardtime_default_on is set, hardtime is supposed to be enabled in every buffer. This is what the README says.

The following line [link to source] does this:

autocmd BufRead,BufNewFile * call s:HardTime()

However, when creating a new buffer that does not yet have a name (e.g. using :tabnew), the BufNewFile event will not fire, and hardtime will not be run. The same is true for buffers that are opened by a plugin: opening a netrw window (:Ex) doesn't enable hardtime, which means that the user can freely use the hjkl and arrow keys.

Is this behavior intended? If not, this commit could possibly help.

First of all, thank you for the great plugin! It really helps to boost productivity and to break the bad habits.

I have one problem with it, it clashes with kana's vim-arpeggio. I thought it was a problem in vim-arpeggio and so I reported the issue in kana's repository. He pointed out that the problem is in the way the mappings are defined in vim-hardtime:

kana/vim-arpeggio#21 (comment)

Could this be updated so it doesn't clash with other plugins? Thank you very much.

I use the mutiple cursors plugin: https://github.com/terryma/vim-multiple-cursors

This collides with hardtime however.
If I create 5 cursors, and then press h for instance, only the N first cursors will move where N is the number defined by g:hardtime_maxcount.

Is this problem known and is there a solution for it?

Nice plugin :)

Is there a way to disable it inside the keyword completion mini buffer (^N^P) ?

Adding "w" to the keys and trying to use vim-wordmotion results in:
E109: ':' missing after '?'

The problem seems to be with the arguments, so:
let mapping["rhs"] = substitute(mapping["rhs"], "'", "''", "g")
But know I get E117: Unknown function.

This works for me, but I don't know if it is equivalent (there's a reason to execute rhs and not the key itself?):

fun! s:RetrieveMapping(key, mode)
    let mapping = maparg(a:key, a:mode, 0, 1)
    if empty(mapping) || mapping["expr"] == 0
        return "'" . a:key . "'"
    endif
    return mapping["expr"]
endf