On 26-Aug-01 Kris Kennaway wrote:
> On Sun, Aug 26, 2001 at 01:20:23PM +0200, Oliver Fromme wrote:
>> "Our" csh still behaves differently like any /bin/csh on
>> any other system that I know, and can't be easily made to
>> behave like them.
> This is an assertion. Where is your supporting evidence?
In his previous message that you didn't read. Geez, I'm a tcsh user myself but
his point is not all that obscure. He mentioned wanting Esc to do instant
filename completion. (Or history, can't remember which). Another one he
referred to is clearly documented in the tcsh manpage that no one seems to read:
(+) 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
expand `!3d' as in csh(1) say `!\3d'.
IOW, to obtain backward compatibility, you have to change your input. That's
not really all that backward compatible since the original interface is broken.
I agree with Andrey that getting the tcsh maintainers to provide backwards
compatibility via a command-line option (or have it triggered when it is
called as csh rather than tcsh) would be the ideal solution.
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message