# What is kakoune equivalent of vim's ';' ? ( jump to next find )

**URL:** <https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976>\
**Category:** Help\
**Tags:** movement\
**Created:** [April 25, 2020, 11:30am UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976 "2020-04-25T11:30:34Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![scr](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/scr/32/486_2.png) [@scr](https://discuss.kakoune.com/u/scr)\
**Post date:** [April 25, 2020, 11:30am UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/1 "2020-04-25T11:30:34Z")

</div>

Hope the title is enough 😛

---

<div class="post-metadata">

**Author:** ![useredsa](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/useredsa/32/419_2.png) [@useredsa](https://discuss.kakoune.com/u/useredsa)\
**Post date:** [April 25, 2020, 12:31pm UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/2 "2020-04-25T12:31:59Z")

</div>

It’s `<a-.>`. `.` repeats the last change and `<a-.>` repeats the last movement.

You check out the mappings inside kakoune with `:doc keys`.

---

<div class="post-metadata">

**Author:** ![duncan](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/duncan/32/95_2.png) [@duncan](https://discuss.kakoune.com/u/duncan)\
**Post date:** [April 25, 2020, 1:19pm UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/3 "2020-04-25T13:19:55Z")

</div>

For new user help try these plugins:  
[basic-interactions.kak](https://bitbucket.org/KJ_Duncan/basic-interactions.kak/src/master/) you get some quick help with key mappings for example:  
 ![new-user-keys](https://discuss.kakoune.com/uploads/default/original/1X/18774b10624b58f9c752dfa3d7f6db5969e8ecf0.png)

And  
[out-of-the-box](https://github.com/lenormf/out-of-the-box) helpful new user experience without the plugin fuss.

Hope this helps. Bye.

---

<div class="post-metadata">

**Author:** ![scr](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/scr/32/486_2.png) [@scr](https://discuss.kakoune.com/u/scr)\
**Post date:** [April 25, 2020, 2:41pm UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/4 "2020-04-25T14:41:17Z")

</div>

Thanks ! I’ll update the wiki on migrating from vim

---

<div class="post-metadata">

**Author:** ![duncan](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/duncan/32/95_2.png) [@duncan](https://discuss.kakoune.com/u/duncan)\
**Post date:** [April 26, 2020, 3:33am UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/5 "2020-04-26T03:33:41Z")

</div>

Sound good, [migrating from vim](https://github.com/mawww/kakoune/wiki/Migrating-from-Vim) ← a good page to know, its provides kakoune insight and vim migration.  
A must know, must use, must have key stroke for every user.  
`<s-[>` is `{` and `<s-]>` is `}`

Updated `basic-interactions.kak` to include the kak info box pictures which should remove the last bit of ambiguity for new users.

Thanks for doing this @scr hope it helps new comers. I still use it so lifers as well. Bye 👋

---

<div class="post-metadata">

**Author:** ![andreyorst](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/andreyorst/32/29_2.png) [@andreyorst](https://discuss.kakoune.com/u/andreyorst)\
**Post date:** [April 26, 2020, 7:38am UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/6 "2020-04-26T07:38:59Z")

</div>

> [@duncan](#):
>
> A must know, must use, must have key stroke for every user.  
> `<s-[>` is `{` and `<s-]>` is `}`

This may not be true for all keyboards, and layouts:

 ![image](https://discuss.kakoune.com/uploads/default/original/1X/ae456264600a3aa7c48ede0a3c1dbe85c3c333d0.jpeg)

Although such keyboards are very rare.

---

<div class="post-metadata">

**Author:** ![scr](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/scr/32/486_2.png) [@scr](https://discuss.kakoune.com/u/scr)\
**Post date:** [April 26, 2020, 10:47am UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/7 "2020-04-26T10:47:17Z")

</div>

Yep, edited the wiki at:  
[migrating from vim](https://github.com/mawww/kakoune/wiki/Migrating-from-Vim)

> `;` become `<a-.>`  
> `<a-.>` is used to repeat the last movement. It work with all the `f` `t` selection, but also with the `<a-i>` and `<a-a>` command. Type `:doc keys` in kakoune for more infos.

---

<div class="post-metadata">

**Author:** ![vbauerster](https://discuss.kakoune.com/letter_avatar_proxy/v4/letter/v/85e7bf/32.png) [@vbauerster](https://discuss.kakoune.com/u/vbauerster)\
**Post date:** [April 27, 2020, 8:17am UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/8 "2020-04-27T08:17:56Z")

</div>

Actually `<a-.>` is useless for `t`, so imho `t` should not be mentioned for `<a-.>`.

---

<div class="post-metadata">

**Author:** ![scr](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/scr/32/486_2.png) [@scr](https://discuss.kakoune.com/u/scr)\
**Post date:** [April 27, 2020, 10:32am UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/9 "2020-04-27T10:32:39Z")

</div>

good point ! it’s weird that it’s part of the official doc. Maybe it’s a bug

---

<div class="post-metadata">

**Author:** ![andreyorst](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/andreyorst/32/29_2.png) [@andreyorst](https://discuss.kakoune.com/u/andreyorst)\
**Post date:** [April 27, 2020, 2:44pm UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/10 "2020-04-27T14:44:03Z")

</div>

no, it’s actually repeats the movement, it just stuck if you’re still right before the character. There was a discussion on if Kakoune should jump over current match to the next one, but it seems there was no implementation for this feature.

---

<div class="post-metadata">

**Author:** ![scr](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/scr/32/486_2.png) [@scr](https://discuss.kakoune.com/u/scr)\
**Post date:** [April 27, 2020, 6:13pm UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/11 "2020-04-27T18:13:13Z")

</div>

Well for my user perspective it’s pretty clear that it should jumps to the next one.

---

<div class="post-metadata">

**Author:** ![duncan](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/duncan/32/95_2.png) [@duncan](https://discuss.kakoune.com/u/duncan)\
**Post date:** [April 28, 2020, 3:53am UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/12 "2020-04-28T03:53:46Z")

</div>

[Key Frequency Heatmap](https://www.keybr.com/layouts); Qwerty, Dvorak, Colemak, Workman.  
Also a nice place just to practice your typing.

---

<div class="post-metadata">

**Author:** ![andreyorst](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/andreyorst/32/29_2.png) [@andreyorst](https://discuss.kakoune.com/u/andreyorst)\
**Post date:** [April 28, 2020, 5:54am UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/14 "2020-04-28T05:54:51Z")

</div>

I see these results to be pointless for programmers. As well as all these “programming” layouts shuffling letters but keeping all special characters away and available only under pinky fingers.

For example on qwerty when using 10 finger touch typing, all these keys are pressed with pinky fingers: []-=~!’;/ as well BackspaceReturnTabShiftL CtrlEscCapsLk. And in comparison only these with ring fingers: )@\>WinR Ctrl, and these with middle ones: \<(\*#$Alt. The rest are pressed with idex %^&. And thumb only used for S p a c e b a r

So what’s funny about that is that pinky is the weakest finger, and it got the most amount of keys - 16! Ring finger is a bit stronger, but got only 5 keys, which is 3 times less. Middle and Index are the strongest ones, while, middle got 6 keys, index only gets 3. And the strongest finger gets **1** huge key to press.

One famous alternative to qwerty is dvorak, and for programmers there is [Programmer dvorak](https://www.kaufmann.no/roland/dvorak/). And it got even more special keys for pinky fingers. Come on!

So in my humble opinion – keyboard layour that is optimized for programming should have all these common operators on the middle of keyboard, accessible by index and middle fingers, Shift, Ctrl and Alt modifiers should be accessed with thumb, as well as S P A C E B A R, and the rest letters are left primarely for ring finger, some for middle and the smallest amount for pinky.

In order to produce such layout we have to mine what letters are least popular in programming languages, and put those to pinky, those who are the most popular should go to ring finger, and those that are little bit less popular for middle, because middle also going to press special chars. All special chars can be arranged by popularity too, but in the middle of keyboard for index fingers to access. Given that we have only 10 keys which hold one special character and a number, we can put those on 5 keys with access via shift or alt. And we do have 5 keys that can easily be accessed by index fingers. And given that thumb will toggle keys state as well, I don’t think that this is a problem.

---

<div class="post-metadata">

**Author:** ![scr](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/scr/32/486_2.png) [@scr](https://discuss.kakoune.com/u/scr)\
**Post date:** [April 28, 2020, 9:13am UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/15 "2020-04-28T09:13:44Z")

</div>

It would be interesting to to parse a lot of random code from git repo and make a frequency analysis. Maybe to it separatly for each language, so we can establish what is the “utlimate layout” for every language.

A second Idea is to have tiny bit different layout for different programming language. I have to change my layout when I code and went I write email. Bascicly the layout just change the coding charactere with charactere specific to my language, the rest is still the same qwerty.  
Imagine changing from am html layout to a C++ layout: the layout is almost the but it remplace \< \> by { } for e. g.

---

<div class="post-metadata">

**Author:** ![andreyorst](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/andreyorst/32/29_2.png) [@andreyorst](https://discuss.kakoune.com/u/andreyorst)\
**Post date:** [April 28, 2020, 9:54am UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/16 "2020-04-28T09:54:11Z")

</div>

Perhaps, once we will end up with screens instead of classic keyboards something like what you describe will be reliable. Until then:

![typing](https://discuss.kakoune.com/uploads/default/original/1X/b28ad09e505a3e4d9ad58750986ba3c2780d91bd.gif)

---

<div class="post-metadata">

**Author:** ![scr](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/scr/32/486_2.png) [@scr](https://discuss.kakoune.com/u/scr)\
**Post date:** [April 28, 2020, 11:28am UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/17 "2020-04-28T11:28:56Z")

</div>

lol nice gif  
Why would you need a screen ? you should not look at your keyboard when typing + changing layout is as easy as `setxkbmap <layout>`

---

<div class="post-metadata">

**Author:** ![andreyorst](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/andreyorst/32/29_2.png) [@andreyorst](https://discuss.kakoune.com/u/andreyorst)\
**Post date:** [April 28, 2020, 12:44pm UTC](https://discuss.kakoune.com/t/what-is-kakoune-equivalent-of-vims-jump-to-next-find/976/18 "2020-04-28T12:44:46Z")

</div>

Well, first of all, screen helps learning different layouts, especially if you’re going to change those for each and every language, as you’ve suggested. Also with screen we can take this idea further, and input unicode, kinda like on mobile. This can be expanded even further to various tools like image editors, so instead of keys we display tool icons. Idea is not new:

 ![image](https://discuss.kakoune.com/uploads/default/original/1X/603f207cdf9f7b89151c05a88aea8775672c4ee7.jpeg)  
But with the screen we have much more control and can add sliders, checkbocs and so on. The keyboard’s only advantage is that we can work without looking at it, but I think this is not due it’s physical presence, because I can type on by phone without looking at keyboard as well. I suggest you to watch [this talk](https://www.youtube.com/watch?v=8QiPFmIMxFc) that is not strictly about this topic, but it illustrates that we’re still using computers as if those were straight out of 80’s.