Gregory Anders
Gregory Anders
> Should we pivote this to track [#28476 (comment)](https://github.com/neovim/neovim/issues/28476#issuecomment-2074250729) though? With https://github.com/neovim/neovim/pull/28650 merged, wouldn't those also belong under the `gr` prefix? E.g. `gri` for implementation, `grt` for type definition.
Could you try something like this? ```vim let g:projectionist_heuristics = { \ "root": { \ "mydir/**/*": { "wildignore": "*.o,*.pyc", "suffixes": "*.h" } \ }} autocmd User ProjectionistActivate call s:activate() function!...
Needs another rebase.
> > Whereas there is no alternative, planned use-case for "gr". > > "gr" could be used for LSP references `grr` is LSP references. `gr` becomes a prefix for a...
>and g as prefix is often used as goto (see native gg, gd, gD) The `g` prefix does not mean goto. `gs`, `gp`, `ga`, `g8`, `g?`, `gJ`, `gu`, `gU`, `gv`,...
>Well is there any reason to not use the mappings that ppl are already used to? Yes, because default mappings have much greater constraints than arbitrary user mappings. If we...
I tried using this crate and ran into the exact same issue. Is there a workaround for the time being?
This also fixes a bug where the `xsct` command was not found even after extracting the tarball because of the version mismatch (the tarball was being extracted under `build/xsct/Vitis/2020.1/` however...