Fixes the crash below by sanitizing the title to not include the
linebreak (replacing it by a "\n" string)
stack traceback:
[C]: in function 'nvim_buf_set_lines'
.../nvim/plugged/plenary.nvim/lua/plenary/window/border.lua:222: in function '__align_calc_config'
.../nvim/plugged/plenary.nvim/lua/plenary/window/border.lua:266: in function 'new'
...are/nvim/plugged/plenary.nvim/lua/plenary/popup/init.lua:384: in function 'create'
...re/nvim/plugged/telescope.nvim/lua/telescope/pickers.lua:326: in function '_create_window'
...re/nvim/plugged/telescope.nvim/lua/telescope/pickers.lua:399: in function 'find'
...m/plugged/telescope.nvim/lua/telescope/builtin/files.lua:151: in function 'v'
...m/plugged/telescope.nvim/lua/telescope/builtin/files.lua:475: in function 'v'
...im/plugged/telescope.nvim/lua/telescope/builtin/init.lua:487: in function 'grep_string'
Fixes#2023
* fix(notify): don't report request on new line
* ref(notify): update message format
* ref(msgs): always quote values + decrease duplication
* fix(ci): undefined variables
* ref(actions): temporary silent actions.__index errors
* cleanup
* revert: panic effort, we continue to use error for those
Co-authored-by: Simon Hauser <Simon-Hauser@outlook.de>
The file_browser now has been fully removed.
Please move to github.com/nvim-telescope/telescope-file-browser.nvim
for a more featureful extension that replaces the builtin file browser.
`builtin.file_browser` will be removed in favor of `telescope-file-browser.nvim`.
Primary rationale for carving out the file browser to an extension:
- Faster development
- Very expansive picker with larger feature set than builtins
We added this for rg 13.0 release because it was needed but it doesnt
seem to be needed anymore. Weird
This might be due to some changes in neovim or due to changes to jobs
this happens if parsers are installed but highlight is set to false.
So parsing the buffer with treesitter will automatically apply them to
the buffer but because treesitter highlighting is disabled it will
change the buffer. Its stupid and i dont know why you want parser
installed but highlighting disabled but whatever.
We just dont calculate highlights for people who have highlight set
to false
After this commit (2460f0a702), the `hl_cache` variable
stores the hl_ID instead of the group name.
Another way to get the hl name which is adopted from the method used
here `_get_hl_from_capture`:
```lua
local hl = vim.treesitter.highlighter.hl_map[query.captures[id]]
```
But, as the method covers another case, we can directly use it.
I've also added the type guard so that, in the future, it does not
explode like it does now.
fixes: #1151
* fix: use treesitter language name if available
This will fix the problem where the filetype is different than the
treesitter lang name. Eg., filetyep -> "sh", langname -> "bash"
* refactor: use treesitter only if the query object is available
* refactor: ok -> parser_ok ;)
