SysV/AT ksh emacs mode broken!

[wtr at moss.ATT.COM]

In article <581 at splut.UUCP> jay at splut.UUCP (Jay "you
ignorant splut!" Maynard) writes:

>I've finally gotten some documentation for ksh (no, I can't pass it 
>along, as I'm not sure of its status), and have run into a problem:
>If I do a 'set -o emacs', I can't edit the history file interactively.  
>It ignores the control characters to move around the line. If I 'set -o 
>vi', command editing works fine.  

>I'd really like emacs mode to work, since I've discovered that I can't 
>stand vi with emacs around. Help!

>Jay Maynard

jay,

this is being posted in advance of any uport technical
response.  so take this answer with a grain of salt ;-) 

the 'bug' in ksh is that the source will not compile under
the large flag.  this has to do with the assumption that the
size of an integer is the size of pointers, etc...

under small model, there is not enough room to fit both the
vi and emacs editting modules in.  so it's one or the other
at link time!  uport took the 'standard' unix editing mode,
vi.

this info is based on e-mail from david korn about compiling
ksh for a 286-based unix box.  i use my 286-box for
work-related  jobs and was trying to port ksh down to it
many moons ago.  (BTW: i gave up once uport posted theirs ) 

to anyone at uport: 

could you please post an alternate ksh with the emacs
command sequences enabled?  just call it ksh-e or something
like that.  it would be much appreciated by the user who
likes the emacs command line editting.  

hope this helps.
=====================================================================
Bill Rankin
Bell Labs, Whippany NJ
(201) 386-4154 (cornet 232)

email address:		...![ ihnp4 ulysses cbosgd allegra ]!moss!wtr
			...![ ihnp4 cbosgd akgua watmath  ]!clyde!wtr
=====================================================================