Taupiqueur

@eikenb We could refuse to source non-POSIX scripts or add a Bash layer (one POSIX and one Bash).

@krader1961 It’s not to add POSIX features to the Elvish language, but to add a layer to compile sources from POSIX scripts.

Automatic as you type completion is about showing all completion candidates for a given token – the same you get when pressing `Tab`. [fish][]’s auto-suggestion is about history and limited...

``` kak hook global NormalKey .* %{ %sh{ selection_count=$(echo $kak_selections_desc | awk -F : '{ print NF }') if test $selection_count -gt 1; then echo exec '' fi }} ```

Maybe jump list could benefit from registers.

For reference: ``` kak # Save selections to the [b]ackup register. hook -group backup-selections global NormalIdle .* %{ set-register b %reg{z} execute-keys -draft '"zZ' } # Add a mapping to...

Prefix the mapping with `` to go back in normal mode where `"bz` can be executed.

Isn’t whitespaces a typo?

Personally, I like my kakrc to be declarative. [kakrc]: ``` kak # Kakoune support # https://github.com/mawww/kakoune/tree/master/rc try %{ source-runtime rc/detection/file.kak source-runtime rc/filetype/asciidoc.kak source-runtime rc/filetype/c-family.kak source-runtime rc/filetype/crystal.kak source-runtime rc/filetype/css.kak source-runtime rc/filetype/eruby.kak...

Having a 0-based variant is fine, especially as when we code we use 0 or 1-based indices.