João Paulo Silva de Souza

Vim issue of interest: https://github.com/vim/vim/issues/3582 If Vim functions do not work for whatever reason, you can try sending the escape codes to the tty directly (example: https://github.com/ardagnir/athame/blob/b1e4c3ccb5739ea2abb62fc7f74cb5a411ab8344/athamerc#L32). ```vim let g:tty='/dev/'.system('ps...

I think the issue should be closed because it has nothing to do with Neovim functionality. It is solved externally and the solution is specific to the user's setup.

My approach to this request is that the editor should not care about that "outside area" you point out, namely the terminal background, because that is managed by the terminal....

The one I care most was not mentioned: colorscheme configuration. Lightline supports a custom dictionary structure for coloring each individual component based on its position. Generally, they are divided between...

:one: Not encoding `args` as JSON has the same whitespace problem, unless you want to separate each in a line. Simplest thing I can think of is ``` ... ```...

I am perhaps sensing some confusion here, so let's confirm the understanding first. My understanding is as follows: # Option 1 core_d adjusts the parsing ## Protocol ``` ... ```...

I understand your idea now. It's similar to the one originally proposed in https://github.com/mantoni/core_d.js/issues/11?_pjax=%23js-repo-pjax-container#issue-860097788, laid out again for comparison: ## Protocol ``` ``` example: ``` { "cwd": "foo", "args": ["bar"]...

Yeah, separating them with a blank line looks better than specifying the line count. I'd agree with that format as well.

Hi @kkoomen it really has been a long time (more than a year!). Since then I've changed the highlighting in my editor to be backed by tree-sitter instead of the...

Your idea is even better than what I was imagining @kkoomen ! If it's not too much trouble, you could omit those type annotations only through a configuration variable, leaving...