Path: utzoo!mnetor!uunet!husc6!bbn!uwmcsd1!ig!jade!ucbvax!cbosgd!osu-cis!tut!karl
From: karl@tut.cis.ohio-state.edu (Karl Kleinpaste)
Newsgroups: comp.os.misc
Subject: Re: What should completion look like on Unix?
Message-ID: <3414@tut.cis.ohio-state.edu>
Date: 21 Dec 87 04:14:45 GMT
References: <1971@cup.portal.com> <1169@nmtsun.nmt.edu> <588@kuling.UUCP> <871@rocky.STANFORD.EDU> <476@athos.rutgers.edu>
Organization: OSU
Lines: 21
In-reply-to: hedrick@athos.rutgers.edu's message of 20 Dec 87 19:25:16 GMT


hedrick@athos.rutgers.edu writes:
   Lock the
   people responsible for tcsh and Gnu emacs in a closet and don't let
   them out until they agree on a single character to use for file name
   completion (tcsh uses ESC, Emacs uses TAB).

You needn't be so hard-hearted about that.  Paul put a number of the
features of my line-editing csh into his tcsh, but his editor still
doesn't allow the arbitrary binding of keys to command functions.  If
you allow such a feature, then you provide one default and allow Joe
Random to do what he will.  I have a file ~karl/.bind which specifies
that both ^[ and ^I do a "recognize" function, which is what the
completion function does.  Piece o'cake, took maybe 10 minutes to
write that particular hunk of code 2 years ago.

(My line editor [land-locked tho' it may be] does both vi- and
emacs-style editing based on a dispatch table of ASCII chars.  T'ain't
tough to write code that diddles the function pointers in that table
based on a new "bind" command...)
-- 
Karl