zc he

> ah, that makes sense. sorry i'm such a noob on this nvim stuff. trying to get up to speed. This nvim-ts config is really confusing, I still don't know...

@fdncred Sorry for not making it clear, actually these are exclusive solutions, not steps to follow. If you choose method 2, you still need to install tree-sitter-nu (using a plugin...

@fdncred that's weird, if you don't remove tree-sitter-nu, it should work fine (need to update to the latest) without requiring to manually copy the scm files. Manually copying just solves...

> Didn't add any tests, but did manually try the following: Should be easy to test by measuring `SemanticSuggestion.suggestion.span`?

@ysthakur, I get confused when actually trying to use this feature. How should I set the span start properly? I mean in a complicated input like `ls | foo `....

> Yeah, it has this really weird behaviour. > > - `commandline` in inaccessable in the completion function > - `$context` only provides args of the current function of the...

> > You want $pos to be relative to current command start? Will it be a breaking change? > > > > Yes, but it doesn't matter anyways. Because before...

> Hmm, I see. > > > > > There's a long existing TODO note for changing this behavior > > > > Can you mention the issue https://github.com/nushell/nushell/blob/c8549448452d28d1a2fbf17ecc63b331c303374c/crates/nu-cli/src/completions/completer.rs#L191 BTW,...

> That said, for advanced cases like this, I think the LSP should have its own logic, and the nu-cli completion logic can remain "dumb." That's what it is now....

If the implementation is that similar to `alias`, why not make it an argument of alias command？