dsill@RELAY.NSWC.NAVY.MIL (03/16/89)
>Do any of you have the ksh >style enhancement to shell.el? Dave Sill? which one of the various >shell.el enhancements adds [kt]sh style command line history editing >to shell.el? I have a copy of Wolfgang Rupprecht's ksh enhancements: shellext 87-10-12 W. Rupprecht, <wolfgang@mgm.mit.edu> Ksh-like extensions to shell. Excerpted from his posting: ;This is a ksh-like extention to shell.el. These extentiions implement ;command history (backwards, forwards, back-search, forward-srearch), ;filename completion, and history printout for an emacs shell window. ;The one glaring difference between this and ksh, is that all of the ;shell-mode commands are bound to the Control-C prefix map. (Eg. ;previous command is C-c C-p). ; ;The full list of shell commands is: ; ; C-c C-a shell-beginning-of-line ; C-c C-c interrupt-shell-subjob ; C-c C-d shell-send-eof ; C-c C-h Prefix Command ; C-c TAB shell-filename-expand ; C-c RET shell-push-input ; C-c C-n shell-next-command ; C-c C-o kill-output-from-shell ; C-c C-p shell-previous-command ; C-c C-r shell-history-search-backward ; C-c C-s shell-history-search-forward ; C-c C-u kill-shell-input ; C-c C-w backward-kill-word ; C-c C-x Prefix Command ; C-c C-y copy-last-shell-input ; C-c C-z stop-shell-subjob ; C-c ESC Prefix Command ; C-c C-\ quit-shell-subjob ; C-c [ show-output-from-shell ; C-c h shell-list-history ; ;This is a diff for shell.el(18.49) (to add a few hooks, and some ;personal bug-fixes/hacks) and a file shellext.el, which does the real ;work. ; ;This basic code has been running on 18.26 as well as 18.49, so you ;shouldn't have much trouble, even on older emacses. I'll be happy to send it out to anyone who provides me with an adequate address or uunet-based path. ========= /* * This means that the return which is executed * immediately after the call to artu actually returns * from the last routine which did the savu. * * You are not expected to understand this. */ -- Comment in UNIX Sixth Ed. Kernel
dsill@RELAY.NSWC.NAVY.MIL (03/22/89)
Several people have asked me for the recently re-posted "shellext" package by Wolgang Rupprecht. I've tried to reply to all requests and verify that they really want me to send it anyway. In my message I said I'd gladly send it to anyone who could give me an adequate address or uunet-based path. Unfortunately, not everyone requesting the package did that, so I wasn't able to reach them. ATTENTION: Just because you can send a mail message to somebody on the Internet, there is no guarantee that they'll be able to reply. Remember, not every system has exactly the same host table. Another problem is that local hosts are often not known outside of the local area. So when you want to be sure that the recipient of your message can reply, include in the body of the message (because mailers tend to fiddle around with addresses in headers) a return address that you are sure is reachable from a host with the standard Internet host table. When in doubt, include several variations in case one fails. So, if you still want a copy of "shellext", I'll be happy to send it to you, provided you give me an adequate return address and mention that you're aware it was recently reposted. ======== "Though a program be but three lines long, someday it will have to be maintained." -- The Tao of Programming
liberte@m.cs.uiuc.edu (03/22/89)
This is worth repeating: > /* Written 2:16 pm Mar 21, 1989 by dsill@RELAY.NSWC.NAVY.MIL in m.cs.uiuc.edu:comp.emacs */ > ATTENTION: Just because you can send a mail message to somebody on the > Internet, there is no guarantee that they'll be able to reply. > Remember, not every system has exactly the same host table. Another > problem is that local hosts are often not known outside of the local > area. So when you want to be sure that the recipient of your message > can reply, include in the body of the message (because mailers tend to ^^^^ > fiddle around with addresses in headers) a return address that you are > sure is reachable from a host with the standard Internet host table. > When in doubt, include several variations in case one fails. In fact, dsill, you ought to have included an address in your posting, if you wanted people to email replies - which now that I think of it, maybe you didnt. We are still in the dark ages regarding email and networks in general. Carry a torch at all times, but resist touching the flame. Dan LaLiberte uiucdcs!liberte liberte@cs.uiuc.edu liberte%a.cs.uiuc.edu@uiucvmd.bitnet