I have put together my own bash debugger (I like it better than the
others I've seen), and wanted to have variable name auto completion in
the 'read' built-in, just like it is in the base command line. Is
there a reason that bash uses a readline that is differently
configured in the 'read' builtin
On Mär 31 2022, Chet Ramey wrote:
> So is this the scenario? If you have
>
> echo 1
> echo 2
> echo 3
> history
>
> in your history, type ^P^P^P to get back to the `echo 2'. Add `24' to
> the end, type ^A^F so the cursor is after the `e', then run
> history-search-backward? Hit the `echo 1' and
On 3/31/22 5:14 AM, Andreas Schwab wrote:
Unfortunately I still see clobbered history lines. When moving to a
previous history line, editing it, and then invoking
history-search-backward and accepting it, the editing remains on this
line (as of before history-search-backward), without a way to
On 3/30/22 7:48 PM, Steffen Nurpmeso wrote:
Chet Ramey wrote in
:
|On 3/30/22 11:16 AM, willi1337 bald wrote:
|> Bash Version: 5.1
|> Patch Level: 16
|> Release Status: release
|>
|> Description:
|>
|> A deeply nested and incorrect regex expression can cause exhaustion of
|>
Unfortunately I still see clobbered history lines. When moving to a
previous history line, editing it, and then invoking
history-search-backward and accepting it, the editing remains on this
line (as of before history-search-backward), without a way to undo it
(the undo list is empty).
--
