On Mon, Dec 09, 2002 at 04:58:25PM -0500, Greg A. Woods wrote:
> >   good if you want to e.g. change the flags
> >   given to the current command
> 
> if that's all you want to do then what's wrong with <CTRL-P>?

I don't get this: CTRL-P gives me the previous line?
So what if I wrote
# /some/long/path/command -options some arguments here
and then find out I need more options; with bash I can do
CTRL-R - and the cursor is at the start of the options.

> > . <UP><DOWN> doesn't give back an empty line
> >   bash does this; ksh remains on the last line in the history
> 
> That's a good thing!  :-)  (^U is your friend here)

Not if you want to look what the last thing was, and not changed
the output of CTRL-Y. But I guess CTRL-C also works.

> If you want a one-key clear(1) then it should be easy enough for you to
> make a custom key binding to work as you wish.

In pdksh? How exactly?

> > . first command line argument gets expanded even to non-executable files
> >   bash does this, and I think it's a useful feature.
> 
> No, that's an annoying useless behaviour.  :-)

Why would I want the first file on my command line not to be executable?

Bye,
 Thomas

-- 
Thomas Klausner - wiz@danbala.ifoer.tuwien.ac.at
What is wanted is not the will to believe, but the will to find
out, which is the exact opposite. -- Bertrand Russell