The yank-last-arg ("_") command and comments

[Thomas Mellman]

A recent new version of bash has changed the behavior of the
yank-last-arg command ("_").  Is there a way to revert to the old behavior?

Now, it no longer does so for comment lines.

i.e. yank the last arg.

A very frequent thing that happens to me is that I discover
after typing in a command line that the object of the command hasn't
been properly readied.

For example, I want to put a file somewhere, and then remember
that the subdirectory hasn't been created yet.  The yank-last-arg command
is very useful in combination with the insert-comment command:

I just hit "#" to turn the command into a comment,
and then enter the necessary command and hit 
(i.e.  XTerm ...F1: string(0x1b) string("_") \n\ ...)

mkdir 

then I can bring back the commented-out line, x-out the comment character,
and rerun it with just a very few key-presses.

--
---
Thomas Mellman  Tel: +49/8233/389-037

   Creative Telcom Solutions

[EMAIL PROTECTED] Fax: +49/1212-5-115-48-103



___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash

Re: The yank-last-arg ("_") command and comments

[Andreas Schwab]

Thomas Mellman <[EMAIL PROTECTED]> writes:

> A recent new version of bash has changed the behavior of the
> yank-last-arg command ("_").  Is there a way to revert to the old behavior?

histchars='!^ '

ie. disable the history comment character.

Andreas.

-- 
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash