[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

^Z signal



>>>>> On Monday, Richard Brooksby <richard@harlequin.co.uk> said:

Richard> pete@minster.york.ac.uk wrote:

> If people must have line editing then they can use ile, or atty, or
> any one of the other pty-based front ends; they also have the
> benefit that since they grab all the input and pass it on to the
> shell or whatever it's running, they work for _all_ programs, not
> just the shell.

Richard> I wasn't aware of these packages, although I've thought that a
Richard> pty-based editor was the `correct' thing to do for ages.  Can you tell
Richard> us where we can find them, or information about pty-based editors?
Richard> (I've tried archie.)

Guess you didn't try hard enough.  Here are a few hits:

unix.hensa.ac.uk:/pub/uunet/usenet/comp.sources.unix/volume25/ile.Z
ftp.uu.net:/usenet/comp.sources.unix/volume25/ile.Z
cnam.cnam.fr:/pub/Archives/comp.sources.unix/ile
irisa.irisa.fr:/News/comp.sources.unix/volume25/ile.Z
lth.se:/pub/netnews/sources.unix/volume25/ile.z

The trick was to ask archie to search for the regexp ^ile, as the
string "ile" is too likely to occur in oodles and oodles of names.

I compiled ile and find it quite satisfactory, so I have now relinked
es without the editline library.  Only problem with ile so far is a
rather hackish way to get the current working directory for file name
completion purposes:  You hit escape-p, and it issues a pwd command to
the shell and reads the resulting output!  Not too cool if you're in
the third line of a multiline command, but...

ile appears to be a lot more portable than atty.  Except, I can't use
gcc:

; make 'CC=gcc ile'
gcc ile -g   -c ile.c -o ile.o
gcc: ile: linker input file unused since linking not done
cc -o ile ile.o -ltermcap
ld: Undefined symbol 
   ___main 
Compilation failed
make: *** [ile] Error 2

This is totally mystifying to me.  It compiles fine with plain old cc,
though.

- Harald