Dimitri Sabadie

Cannot use inline highlights in provider

2

Hello, I have a custom provider for LSP using [lsp-status](https://github.com/nvim-lua/lsp-status.nvim). The way this is structured: ```lua local lsp_status = require('lsp-status') lsp_status.register_progress() lsp_status.config { current_function = true, kind_labels = symbol_kind_labels_map, status_symbol...

Allows the user to provide their own custom char for indents.

9

Relates to #6.

Add support for scanning down files by using treesitter / tags

1

[treemacs](https://github.com/Alexander-Miller/treemacs) has this super cool feature where pressing `` on a directory opens a it to show the files, but pressing tab on a file opens it in the tree...

Empty directory / open empty directory icons don’t look correct

3

Hello! Unicode characters `f114` and `f115` refer to empty directory / opened empty directory in fontawesome / nerdfont (example [here](https://github.com/kyazdani42/nvim-tree.lua/blob/master/lua/nvim-tree/config.lua#L20-L21)). However, when using `nonicons` in nvim, you can notice that...

Haskell highlighting is broken

7

I had to remove the overridings from gruvbox to get a decent syntax highlighting back. There’s some kind of regression. Is there a way to fix that?

C/C++ color hilighting is pretty poor

3

This is the current status of hilighting in my neovim:  Comparison with Atom, for instance:  I...

Incoherent parameter order

1

I have an endpoint that mixes both `ReqBody` and `QueryParams`: ```haskell filterOccurrences :: [Tag] -> [QueryFilter] -> … ``` However, the generated Elm reverses the order: ```elm postOccurrencesFiltered : List...

Remove rustc_serialize.

3

The crate has been deprecated for quite a while now. Time to move on. :)

feature: Allow toggle (hide/show) of panes outside of the viewport

8

Both bar should be allowed to be hidden, potentially even dynamically (my workflow in tmux relies a lot on hiding the statusbar to use all the screen estate). I will...

Try to optimize the expression parser

2

Some benchmarks are needed to ensure what the problem is, but I’m pretty sure (given the current `nom-3` implementation) that we have a lot of failures and retries.