-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Up- and Down- Arrow should consider entered text #465
Comments
This will be a feature for |
@Flare576 Does the right-arrow completion work for you? Or I agree that this would be nice too, and also that it's an upstream issue. |
@wycats Right-arrow completion does take the value displayed in white and enter it as the current command. I'm 99.9% sure we're on the same page, but just to future-proof this issue: my request would be to, essentially, filter the history based on the already entered partial command, not just maintain the right-arrow functionality. |
Is there an update on this? I'm very used to typing the beginning of a command and using arrow-up a few times to find a command in my history from the zsh feature and would love to see it in nushell. If you can give me some hints I'm willing to implement this feature and create a PR. |
@oberien - we currently use https://github.com/kkawakam/rustyline to do our line editing. If it gets implemented there, we should be able to add it nushell. You might want to file an issue on that repo and see if it's being worked on. The bonus is that other people using rustyline would also benefit. |
Why won't they accept the pull request? |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
!notstale |
This issue is being marked stale because it has been open for 90 days without activity. If you feel that this is in error, please comment below and we will keep it marked as active. |
This is not stale. |
* Sort default context items categorically * Separate commands in multiple statements * Use curly braces instead of square brackets This prevents undesired reformatting.
* Sort default context items categorically * Separate commands in multiple statements * Use curly braces instead of square brackets This prevents undesired reformatting.
Solved with the history traversal behavior of reedline |
* Upgrade vuepress to v2 and add dark mode support * Fix code snippets importing * Fix nav item titles * Fix some broken tables * Fix blog, serch and command reference * Fix doc building for vuepress-next, avoid using angle brackets * Fix broken tables
I have slightly different case, where I'd like arrow up to match commands that contain the text I've entered, not just commands that start with the text. I'm currently running nushell 0.71.0, but I also couldn't find any mention of this feature in any following release notes. |
When I type in a partial command and press ⬆️, I expect to only see historical commands starting with my partial. Example:
I'd expect the line to now have
cd /a/really/long/path
, but it actually hasls
The text was updated successfully, but these errors were encountered: