void-linux / void-linux/void-packages

[bash] / since 5.3 history and partial search is unusable

Open
#57,710 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-testing
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
  1. when i press "a[arrow up]" i get "appCLI LDR nick:9000..9100 "M:UHUB rdK0x2001C000+128." < /dev/null"
  2. then i move the cursor to the L of LDR and type "no"
  3. then i press "[arrow up]" and get "appCLI no nick:9000..9100 "M:AIPA confE^""
  4. then i press "[ctrl]c" and get a new line
  5. 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
  1. fill the history with some commands (some of them start with the same 3 letters)
  2. enter the start X of an old command
  3. press [arrow up] and see the old command C
  4. then edit this old command, so that it is the start of an older command, that also starts with X
  5. then press [arrow up] and see the old command D
  6. press [ctrl]+c
  7. then enter X again
  8. press [arrow up] and see a mixture of C and D

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

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.