The Vim-Inspired Editor with a Linguistic Twist

Resources
1

https://cosine.blue/2019-09-06-kakoune.html

2 Likes
2

Maybe next year, Emacs. I really want to like you.

So me. Also, judging by the site design (buttons), (they (love) (lisp) (or (something) (like that))).

Some notes:

6.3 Persistent configuration

Let’s say you’ve mapped a few keys and set a few options. How do you make them persistent between kak(1) sessions?

Create the file $HOME/.config/kak/kakrc and place your mapping and options in there. This is the analogue to one’s $HOME/.vimrc .

When you start kak(1), before sourcing your kakrc it first sources all *.kak* files within your $HOME/.config/kak/autoload/ directory. That means you can put anything—even Git repositories in there (i.e. plugins)—and all non-Kakoune files don’t cause Kakoune any grief.7

Once your autoload directory exists, however, Kakoune decides not to source the system run-time files under /usr/share/kak/autoload/ , so you’ll want to link that system directory symbolically into yours:

    mkdir $HOME/.config/kak/autoload/
    ln -s /usr/share/kak/autoload/ $HOME/.config/kak/autoload/

I feel like most of users stumble on this problem of creating autoload and observing that editor no longer works. Then after some googling/reading man they understand that system autoload no longer works. It looks more like a bug for me, and that’s why I make plug.kak.

is by convention that the uppercase ‘WORD’ refers to whitespace-separated groups of characters, whereas the lowercase ‘word’ refers to consecutive runs of alphanumeric characters.:leftwards_arrow_with_hook:︎

Whitespcace separated? I guess they mean that WORD includes non word characters as part of a WORD, but not whitespace.

GNU readline(1) is the line-editing library used by countless terminal-based programs. I now use Emacs bindings in Readline, because they differ enough from Kakoune that I don’t get confused.:leftwards_arrow_with_hook:︎

Kakoune supports some readline shortcuts in the prompt area, which is nice.

1 Like
3

Hey, thanks for posting my article here!

is by convention that the uppercase ‘WORD’ refers to whitespace-separated groups of characters, whereas the lowercase ‘word’ refers to consecutive runs of alphanumeric characters.:leftwards_arrow_with_hook:︎

Whitespcace separated? I guess they mean that WORD includes non word characters as part of a WORD, but not whitespace.

I didn’t know how else to describe it really. By whitespace I mean spaces, tabs and newlines.

Kakoune supports some readline shortcuts in the prompt area, which is nice.

Yeah but they’re not quite the same, which is a bit frustrating at times. Alt+f and Alt+b for example should skip symbols and punctuation characters.

4

Welcome to the forum @chambln - since no one welcomed me, I will welcome you!

Looking forward to other articles.

1 Like
5

I love the pandoc emoji trick :green_heart:
Good read @chambln, thanks.

1 Like
6

Related discussion on reddit: https://www.reddit.com/r/vim/comments/d7b6y1/the_viminspired_editor_with_a_linguistic_twist/

7

Lobsters thread: https://lobste.rs/s/rukhsx/vim_inspired_editor_with_linguistic
I forgot to post it here, sorry

1 Like