From owner-freebsd-current Mon Aug 27 9:26:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id CE60737B405 for ; Mon, 27 Aug 2001 09:26:45 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id JAA11268; Mon, 27 Aug 2001 09:26:27 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010826140236.A21698@xor.obsecurity.org> Date: Mon, 27 Aug 2001 09:26:33 -0700 (PDT) From: John Baldwin To: Kris Kennaway Subject: Re: Why is csh tcsh? This can be a bad thing... Cc: freebsd-current@FreeBSD.org, Oliver Fromme Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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. > Kris -- John Baldwin -- 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message