Rom Grk

Ok sure, you can probably re-use [nerdfont's script](https://github.com/ryanoasis/nerd-fonts/blob/master/font-patcher). I'll wait for patched fonts then.

Forget all of the above. The root cause is a namespace conflict with https://github.com/notomo/promise.nvim. Both that plugin and your `promise-async` try to use the `require('promise')` namespace in lua.

Both installed with vim-plug. If you see on that repo, they use `./lua/promise.lua` as well. You'll need to decide by a duel who keeps the name. Ping @notomo. The best...

@logicalparadox up. This can make you loose quite a lot of time. I won't make the mistake again, but think that every developer that makes the mistake of running `npm...

I don't think it would be too hard to implement. We could expose the required functions to retrieve the context window ID. From there, you can read the lines in...

Great, thanks, that answers my questions :) Can't wait for that chapter then.

From vim doc: ``` :e[dit] [++opt] [+cmd] Edit the current file. This is useful to re-edit the ``` Short forms of commands are hard-coded, not matched from a substring search....

Mmm, ya, you might be right about the `regex` thing not being useful. Still, the `Array` is useful. Eg, for `edit` we need to hard-code both `e` and `edit`. Thus,...

You will still need an entry ``` coffee 'e': priority: 1 callback: BufferCommands.edit # in addition of 'edit': priority: 1 callback: BufferCommands.edit ``` instead you could write: ``` coffee 'edit':...

Because there are other low-priority entries. `'e'` is defined as `'edit'`. If it wasn't, it would first match, eg, `'echo'`. Using a priority-system _instead_ of hard-coding shorthands would be longer....