ESC p is history in *shell*, in bash, C-p

ESC p is history in *shell*, in bash, C-p

[Dan Jacobson]

Do you find, after using a *shell* window for half an hour, and then
going back to a usual non-emacs bash session, you carry over the ESC p
history recall habit, for a few accidental commands, even though you
wonder why you don't know better, and should be hitting C-p, being
that you only use a emacs *shell* window 2% of the time.

Does this "indicate" (as they say in medicine) that in non-emacs bash
one should bind ESC p and ESC n to do the same as C-p and C-n?

But wait, why should I let this little punk ESC p dominate the C-p
I've used for years?   The answer must lie in correcting the brain
splitting design flaw that has existed for ~20 years; we must make C-p
somehow behave in *shell* ... hmm, perhaps a vi-like mode switching,
"now I want to be on the command line", "now I want full editing over
the buffer contents".  Throughout this it doesn't seem to make sense
to allow the user to alter the output of previous commands... oh, that
is besides the point.

Anyway, an undeniable brain splitter.  One of my goals in using free
software was that never again would I be "forced" to have my brain
split...

> then rebind the keys, silly.

it's not that simple. 

(Yes emacs also has a terminal emulator with C-p for history... but
then I wouldn't have started that window in emacs in the first
place... mainly for easy copying of output...)
-- 
http://jidanni.org/ Taiwan(04)25854780

Re: ESC p is history in *shell*, in bash, C-p

[Kai Großjohann]

jidanni@deadspam.com (Dan Jacobson) writes:

> Do you find, after using a *shell* window for half an hour, and then
> going back to a usual non-emacs bash session, you carry over the ESC p
> history recall habit, for a few accidental commands, even though you
> wonder why you don't know better, and should be hitting C-p, being
> that you only use a emacs *shell* window 2% of the time.

I like eshell's behavior: when after the shell prompt, C-p means
backward in history, elsewhere in the buffer it moves point.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)

Re: ESC p is history in *shell*, in bash, C-p

[Andreas Schwab]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai writes:

|> jidanni@deadspam.com (Dan Jacobson) writes:
|> 
|> > Do you find, after using a *shell* window for half an hour, and then
|> > going back to a usual non-emacs bash session, you carry over the ESC p
|> > history recall habit, for a few accidental commands, even though you
|> > wonder why you don't know better, and should be hitting C-p, being
|> > that you only use a emacs *shell* window 2% of the time.
|> 
|> I like eshell's behavior: when after the shell prompt, C-p means
|> backward in history, elsewhere in the buffer it moves point.

That doesn't seem to be the default.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: ESC p is history in *shell*, in bash, C-p

[Kai Großjohann]

schwab@suse.de (Andreas Schwab) writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai writes:
>
> |> I like eshell's behavior: when after the shell prompt, C-p means
> |> backward in history, elsewhere in the buffer it moves point.
>
> That doesn't seem to be the default.

Oh.  I wonder which customization did this.  Hm.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)