How does ied work?

How does ied work?

Post by Alwyn T » Sun, 09 May 1993 02:47:51


Does anybody know of a public domain version of ied on HP-UX?

I'm trying to find out how ied invokes a utility program and
positions itself as a frontend, and particularly how it handles
I/O. I'm reading the source of a public domain ksh to get some
ideas at the moment but it's difficult and time consuming.

What system calls are used and how are stdin/stdout handled... etc.?


Alwyn Teh


ied(1)                                                               ied(1)

      ied - input editor and command history for interactive programs

      ied [-dirt] [-h file] [-s size] [-p prompt]
              [-k charmap] utility [arguments...]

      ied is a utility command that is intended to act as an interface
      between the user and an interactive program such as bc, bs, or Bourne
      shell, providing most of the line editing and history functionality
      found in the Korn shell.  ied interprets the utility name as the
      command to be executed, and passes the arguments as the arguments to
      the utility.  Subsequent input to utility then has access to editing
      and history functions very similar to those provided by ksh.

      ied monitors the state of the pty it uses to run the command, and
      whenever the application it is running changes the state from the
      state of the tty when ied started, ied becomes "transparent".  This
      allows programs to do shell escapes to screen-smart programs.  In
      general, ied should not in any way interfere with any action taken by
      any program for which it provides a front end.  This includes Korn
      shell itself: in this case ied would provide history for any
      application that was run by ksh,  and ksh would provide its own
      independent history.  In a useful extreme case, ied can be used as a
      front end to the login shell (which might be ksh or csh).  In this
      case, all applications that use normal line editing gain line editing
      and history, sharing a single history.  The shell would continue to
      have its own independent history if it provides such a mechanism.

      When ied is in its transparent mode, no history is saved.  In
      particular the "ex" mode of vi does not use normal line editing
      (rather, it simulates it) and ied cannot provide history in this case.
      The Subject: and address line editing of mailx also is not editable
      with ied.



1. ied not working


  I am facing problems using ied. When i type

$ ied sqlplus user/pass

  it just hangs. If i do a ^c to get out, it prints the following

ied: final TCSETA ioctl failed: Not a typewriter
ied terminating.

   A uname -r on my m/c give me this B.11.00 And a what on my ied give
me "ied version 82.3  97/09/10".  My TERM is set to vt100 (i am using
a telnet session).

   Would appreciate any help to fix the problem.

Thanks in advance,

2. what bus architecture should I choose for my custom DAQ board?

3. How to make pcmcia ethernet card that works with Linux work with dos? . .

4. two netork cards and ELF

5. Solaris equivalent of HP-UX's 'ied' command

6. proftpd authentication via nis

7. fed, ile, ied

8. tar everything except *.A and xx.B

9. ied with csh?

10. SSRT2421 Security Vulnerability in ied(1)

11. Ied utility equivalent for HP-UX

12. Solaris equivalent of HP-UX's 'ied' command

13. ied Error