Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Under Bash some behavior of Alt+d has been driving me crazy since years and I figured out that maybe it could be fixed with a setting.

If I'm at a terminal and issue a command like this:

...$   cat >> ~/notesSuperLongFilename.txt

and then if I want, say, to issue :

...$ scp ~/notesSuperLongFilename.txt

I'd like to get back the "cat >> ~/notesSuperLongFilename.txt" using Ctrl+p (previous line) and then do Ctrl+a and then Alt+d and Alt+d again so I'd have:

...$  ~/notesSuperLongFilename.txt

and then I'd be able to simply enter "scp" and then do a Ctrl+m (or hit Enter / Return).

However it doesn't work because after the first Alt+d I get:

...$ >> ~/notesSuperLongFilename.txt

(so far so good)

but after the second Alt+d I get:

...$ .txt

So for some reason Alt+d deletes ">> ~/notesSuperLongFilename" at once instead of just deleting ">> ".

This has to be the single biggest time-waster that is driving me crazy with Linux / Bash since literally years.

So how can I fix this (arguably broken) behavior of Alt+d?

P.S: I don't know who's "responsible" for that Alt+d behavior: I don't know if it's the terminal or if it's the shell (Bash in my case).

share|improve this question
after "cat >> ~/notesSuperLongFilename.txt", type "scp " and then Esc,. (Escape one time and then the "." character one time) – Mathieu Jul 5 '13 at 19:13
up vote 3 down vote accepted

I don't know who's "responsible" for that Alt+d behavior: I don't know if it's the terminal or if it's the shell (Bash in my case).

It's bash, specifically the default command-line editing setup. Here is a nice page on what commands can be bound, and how to change the default bindings.

The default binding for Alt-d is kill-word which is supposed to work like the command of the same name in Emacs. As you've observed, though, it doesn't—Emacs would consider the space between >> and the tilde in your example to be a word break. That bash does not, I would consider a bug. Short of getting the source for bash, changing it, and recompiling it, I don't know what you can do.

share|improve this answer
This appears to be a bug. I'd report it to the Bash team. – Ernie Jul 4 '13 at 19:14

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.