void-linux / void-linux/void-packages
[bash] / since 5.3 history and partial search is unusable
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Is this a new report?
Yes
System Info
Void 6.12.54_1 x86_64 GenuineIntel notuptodate hold FFFFF
Package(s) Affected
bash-5.3_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
- when i press "a[arrow up]" i get "appCLI LDR nick:9000..9100 "M:UHUB rdK0x2001C000+128." < /dev/null"
- then i move the cursor to the L of LDR and type "no"
- then i press "[arrow up]" and get "appCLI no nick:9000..9100 "M:AIPA confE^""
- then i press "[ctrl]c" and get a new line
- then i press "a[arrow up]" and get "appCLI LDR nick:9000..9100 "M:UHUB rdK0x2001C000+128." < /dev/null"
Actual behaviour
but when i use the new version, i get a garbled line, that i never executed:
exec /bin/bash,5.3
appCLI no nick:9000..9100 "M:AIPA confE0"^C
appCLI noLDR nick:9000..9100 "M:UHUB rdK0x2001C000+128." < /dev/null^C
Steps to reproduce
.bashrc
shopt -s expand_aliases
shopt -s cdspell
shopt -s checkwinsize
shopt -s cmdhist
shopt -s dotglob
shopt -s expand_aliases
shopt -s extglob
shopt -s histappend
shopt -s hostcomplete
export HISTSIZE=10000
export HISTFILESIZE=${HISTSIZE}
export HISTCONTROL=ignoreboth:erasedups
- fill the history with some commands (some of them start with the same 3 letters)
- enter the start X of an old command
- press [arrow up] and see the old command C
- then edit this old command, so that it is the start of an older command, that also starts with X
- then press [arrow up] and see the old command D
- press [ctrl]+c
- then enter X again
- press [arrow up] and see a mixture of C and D
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported bash-5.3_1 behavior and reproduce it using the provided .bashrc history settings and command sequence. Compare the expected and actual readline/history results, especially after editing a recalled command and pressing Arrow Up, then verify that the final recalled command is not a mixture of earlier entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100