nushell / nushell/nushell

"where" tab completion

Open
#10,168 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A:completions deprecated:duplicate
Dominant language
Rust
Stars
40.5k
Forks
2.3k
Avg merge
1d 19h
Merged PRs (30d)
85

Description

Describe the bug

Complete nuub here, I don't even know how this is supposed to work, please be gentle :)

Imo, the tab comletion for where doesn't work like expected, it completes files instead of key words as shown in https://www.nushell.sh/commands/docs/where.html.

How to reproduce
  1. type ls | where
Expected behavior

I'd like to see which key words can be used with where as completion

Screenshots

image

Configuration
| key                | value                                                            |
| ------------------ | ---------------------------------------------------------------- |
| version            | 0.84.0                                                           |
| branch             | makepkg                                                          |
| commit_hash        | d2abb8603abab43ec4a6d4ed56f9018790b99dce                         |
| build_os           | linux-x86_64                                                     |
| build_target       | x86_64-unknown-linux-gnu                                         |
| rust_version       | rustc 1.71.1 (eb26296b5 2023-08-03) (Arch Linux rust 1:1.71.1-1) |
| cargo_version      | cargo 1.71.1                                                     |
| build_time         | 2023-08-23 02:21:39 +00:00                                       |
| build_rust_channel | release                                                          |
| allocator          | standard                                                         |
| features           | dataframe, default, extra, sqlite, trash, which, zip             |
| installed_plugins  |                                                                  |
Additional context

Thanks for this awesome shell !

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with ls | where followed by Tab on the reported Nushell version, then trace the where command's tab-completion entry point. Compare the result with the keyword list shown in the linked where documentation; done means keyword suggestions appear instead of file completions.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, shell
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.