bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bash History Behavior Suggestion


From: Greg Wooledge
Subject: Re: Bash History Behavior Suggestion
Date: Mon, 19 Aug 2024 16:26:45 -0400

On Mon, Aug 19, 2024 at 15:52:22 -0400, support@eggplantsd.com wrote:
> I would suggest:
> 2. Restrict up-arrow completion to the history of present session.

This is going to be an *extremely* unpopular suggestion.

Though, I must wonder: do you literally mean *only* the up-arrow (or
Ctrl-P or ESC k), or do you also include searching from within
the interactive shell's editing modes (Ctrl-R or ESC /)?

My own usage pattern includes using ESC / to bring up a historic command
from a past session.  I do this a *lot*.  I suspect others may share that
pattern, albeit possibly with the emacs key binding instead of the vi one.

I don't know how common it is to use the up arrow (or equivalent) to
bring up a command from a past session.  I've done it a few times --
usually when I'm trying to answer someone's question, and I launch a
temporary shell window to do so, get my answer, paste it to them, close
the window -- and then suddenly they change the question.  So I open
another new window, and bring up the command(s) I was just using in the
previous window, modify them, etc.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]