home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.shell
- Path: sparky!uunet!mcsun!sunic!ugle.unit.no!news
- From: Harald.Eikrem@delab.sintef.no
- Subject: Re: tcsh in the future - what should it be like?
- In-Reply-To: Harald.Eikrem@delab.sintef.no's message of 31 Jul 92 01:09:03
- Message-ID: <1992Jul31.152929*Harald.Eikrem@delab.sintef.no>
- Sender: news@ugle.unit.no (NetNews Administrator)
- Organization: SINTEF DELAB, Trondheim, Norway.
- References: <yeates.711122638@beryl17> <1992Jul16.153506.24366@bmerh85.bnr.ca>
- <1992Jul27.031238.10376@chpc.utexas.edu>
- <1992Jul27.215202*Harald.Eikrem@delab.sintef.no>
- <smr.712419130@hitkw14>
- <1992Jul31.010903*Harald.Eikrem@delab.sintef.no>
- Date: 31 Jul 92 15:29:29
- Lines: 21
-
- tcsh hints --
-
- You may bind e.g. F-keys to perform your 500-times-a-day commands by
-
- bindkey -c key-seq command
-
- and it wont even hit the command history, if that's what you so badly want
- to avoid. You may even
-
- bindkey -c key-seq \!$EDITOR
-
- if you know what I mean.
-
- And a history-search-backward + newline function might be set up as
-
- bindkey -s key-seq '\ep\n'
-
- See? You enter the start of the command you want reexecuted and hit
- the chosen key..... Pling.
-
- ~~h
-