Darren Schroeder
Darren Schroeder
I remember this highlighting at one point. I wonder if it's just a regression. OTOH, I can't even get it to search with / so, who knows?
It works sometimes. Here it's working for `N` but it doesn't work for `NU`. This is `$env | explore`.  I can get the `ls | explore` example working but...
I see. That's neat but strange and broken. I also don't see it moving between hits with `n` and `p` like it used to.
I can get `n` to work but not `p` with `ls | explore`.
Can we land this?
This sounds like a discussion on Discord we just had https://discord.com/channels/601130461678272522/1276981416307069019 https://github.com/nushell/nushell/pull/4674 Here's an excerpt. We're considering removing the functionality that allows custom completions to use different settings than our...
yup, it's overdue. I'm not sure I remember how. LOL
> [@fdncred](https://github.com/fdncred) can the vscode plugin be made to only use `nu --lsp` so we can deprecate the `--ide-*` flags? If they provide anything that `nu-lsp` doesn't, we can just...
We'd accept a PR for these changes. > It doesn't work as listed any more and in any case, it would be good to have an explanation of where 100953...
This bug has haunted me for a while. Thanks for adding an issue for it.