Idan Arye

I looked at the code, and while I don't claim to fully understand it, it does not look like `_is_pytest_func` is at fault. It's purpose is to detect the test...

I'm not sure I understand. ```python def complete_param_names(func): def wrapper(context, func_name, decorator_nodes): module_context = context.get_root_context() if _is_pytest_func(func_name, decorator_nodes): names = [] for module_context in _iter_pytest_modules(module_context): names += FixtureFilter(module_context).values() if names:...

How? I tried putting some prints into `FixtureFilter._filter`, but it does not seem to even look at the star import...

I still don't get why star imports have to be a performance issue. Isn't Jedi already following them for regular completion and introspection?

With [jedi-language-server](https://github.com/pappasam/jedi-language-server). But I figured Jedi needs to offer such a feature before any language server can offer it as a code action.

Language servers do this via code actions. At least - [that's what rust-analyzer does](https://rust-analyzer.github.io/manual.html#add_impl_missing_members). If Jedi offers the backend, the language server can use it to format a code action...

rust-analyzer sets the kind to "quickfix", but it hardly matters - `CodeActionKind` is only used for filtering the generated actions and maybe for IDEs to show an appropriate icon. Inline...

Isn't that how code actions work? Why do you need a special command for that?

So much for having a unified protocol that solves the matrix problem...

I'd like to add that: * When I open two tabs and only then run `NeorgStart`, only the tab that I ran `NeorgStart` from changes its working directory. But when...