csh or tcsh Shell History

[Phishfry]

So since tcsh history is a 'built in' feature it does not have a good manual.

Tell me. I know that tcsh is really csh or linked.

But why does csh history work differently?

It needs more letters to match command history. How can csh be different. Auto-complete acts different?

Is this 'built-in' command of csh history with same name as tcsh history but it acts differently?

 

[Phishfry]

Maybe it is just autocomplete that is different between the two shells and history is the same.

Please enlighten me.

 

[SirDice]

I know that tcsh is really csh or linked.

The other way around actually. It's all tcsh(1).

This is important to keep in mind:

Throughout
       this manual, features of	tcsh not found in most csh(1)  implementations
       (specifically,  the  4.4BSD  csh)  are labeled with `(+)', and features
       which are present in csh(1) but not usually documented are labeled with
       `(u)'.

So, you'll see things like this in the manual:

       (+) While csh(1)	expands, for example, `!3d' to event 3 with the	letter
       `d' appended to it, tcsh	expands	it to the last	event  beginning  with
       `3d';  only  completely numeric arguments are treated as	event numbers.
       This makes it possible to recall	events beginning with numbers.	To ex-
       pand `!3d' as in	csh(1) say `!{3}d'.

Which explains some of the differences when invoked as csh or tcsh.