Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:9915 comp.os.386bsd.bugs:2196 Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!blanket.mitre.org!think.com!cass.ma02.bull.com!as02.bull.oz.au!melb.bull.oz.au!zen!sjg From: sjg@zen.void.oz.au (Simon J. Gerraty) Subject: Re: Returning from X and running ksh Message-ID: <1994Apr26.002906.26630@zen.void.oz.au> Organization: Zen programming... Date: Tue, 26 Apr 1994 00:29:06 GMT References: <CoJDx5.FH5@cbnewsj.cb.att.com> Lines: 28 rudy@cbnewsj.cb.att.com (avram.r.vener) writes: >On a cmpletely different problem, has anyone else experienced the >bugs I found in ksh? When I redirect a simple ls command from the ksh to >a file the files is filled with garbage characters. The output of the ls >redirected into the file, but after all that garbage. Until the next release or patch, you should have compiled pdksh with -D__386BSD__ to prevent a call to fseek() in the stream flush code. > ... Also, hitting the >escape key in ksh does not place me in the command lind editor, and yes I have >FCEDIT defined. Any words of wisdom here? Yes, add set -o vi_or_emacs to your $ENV file to ensure you get what you want. pdksh will check FCEDIT,EDITOR and VISUAL (in that order) to try and detect an editor preference. Also, reporting bugs/problems to maintainer might get quicker response :-) -- Simon J. Gerraty <sjg@zen.void.oz.au> #include <disclaimer> /* imagine something _very_ witty here */