Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!athena.mit.edu!tytso From: tytso@athena.mit.edu (Theodore Y. Ts'o) Newsgroups: comp.unix.wizards Subject: Re: Input Line Editing Message-ID: <6192@bloom-beacon.MIT.EDU> Date: 14 Jul 88 02:26:23 GMT References: <16456@brl-adm.ARPA> <9666@eddie.MIT.EDU> <10443@ulysses.homer.nj.att.com> <9671@eddie.MIT.EDU> <23839@bu-cs.BU.EDU> Sender: daemon@bloom-beacon.MIT.EDU Reply-To: tytso@athena.mit.edu (Theodore Y. Ts'o) Organization: Massachusetts Institute of Technology Lines: 21 One problem with putting the input line editor (ile) where it is is that you don't always want to be able to step back through ALL the lines that were typed to that tty. For example, if you started editing a file using /bin/ed (or some other interactive program), and typed hundreds of "n", "p", "i", "a", and "s/foo/bar/" commands, when you exited to the shell, do you really want to step through those hundreds of /bin/ed commands? The shell isn't going to do anything useful with them. Want I want to do is step back to the last *shell* commands, not necesarilly the last line I typed. Now, you might say that this is a "inconsistent user interface". But I find that having the shell step through only shell commands is a lot more friendlier to the user. I use a csh with a line editor hacked in, and I've been very satisified with the result. This is the csh which is in use at MIT Project Athena, and our users in general like it a lot. - Ted =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Theodore Ts'o mit-eddie!mit-athena!tytso 3 Ames St., Cambridge, MA 02139 tytso@athena.mit.edu If it's for real, it isn't!