Wsevolod
Wsevolod
   Here are configs: [galaxyline](https://github.com/kraftwerk28/dotfiles/blob/master/.config/nvim/lua/cfg/galaxyline.lua), [colors](https://github.com/kraftwerk28/dotfiles/blob/master/.config/nvim/lua/cfg/colors.lua)
I suggest adding only support for tabs (not buffers), like this is done in lightline. bufferline/barbar is intended for displaying buffer list
@kyazdani42, nerdfont patch has various directory icons and [lsd](https://github.com/Peltoche/lsd/blob/master/src/icon.rs#L112) uses them. Though it is probably [web-devicons](https://github.com/kyazdani42/nvim-web-devicons) task to resolve the icon depending on directory name.
For anyone using neovim's builtin LSP, here's a solution: ```lua local jdk_home = "/usr/lib/jvm/java-11-openjdk" -- Your actual jdk path lsp_config.kotlin_language_server.setup { cmd_env = { PATH = jdk_home .. "/bin:" .....
@plcplc, that is something I missed, thank you. Is there any way to build&publish this branch on CI to test out my changes after I fix the issue? My main...
I use this for migrating global packages (assuming we are currently on the newer version): ```bash fnm_upgrade () { fnm exec --using=$1 npm ls --global --json \ | jq -r...
It now works as expected, non-SETOF computed fields don't have `where` / `limit` / `offset` / `order by` / `distinct` clauses and are single value, nullable. 
Note, that this PR introduces the following changes to the GraphQL schema of computed fields: 1. `SETOF `: The return type changed from `[some_type!]` to `[some_type!]!`. That is, if a...
@plcplc, I've added tests for Postgres and BigQuery. Because BigQuery doesn't support `SETOF` modifier, the computed fields for this backend type always act as if the function was `SETOF` (`[some_type!]!`...
> It may be that we'll add a means to make the change opt-in Making a command-line/env-variable flag which would change the behavior is a no-issue for me, although it...