What shell is being used.  I'm using ksh and it works fine under MDK 7.0

Mike Hahn

Chmouel Boudjnah wrote:

> Linda Walsh <[EMAIL PROTECTED]> writes:
>
> > I like to use the vi set of editing commands in my shell.
> >
> > I would put the 'set -o vi' in my .profile.
> >
> > Ok fine.  In the days of RH5.x this worked.  Then RH 6.0 and Mandrake 6.1
> > came out and it broke.  It's still broken in RH 6.1 and MDK 7.0 but it
> > isn't broken in SuSE 6.3.  Have done identical kernels between the distro's
> > and it's still only broken on MDK(&RH), so it's not there.  The bash version
> > *looks* the same.
> >
> > The break is such:
> >
> > If you put the line in above to be automatically executed upon login,
> > you *won't* be able to use line editing, it will just beep at you when you
> > press ESC.  Subsequent attempts to
> > 'set -o vi' have no effect**. If I *don't* put the line in .profile
> > (or .bashrc), then I can manually type it in each time I spawn a window
> > or remote login and that works.
> >
> > ** - Ahh...this is interesting.  On a virtual tty console (ex. CTL-ALT-F2),
> > it ignores the "set -o vi" in the .profile, BUT I can type it in
> > interactively and have it work.  But it doesn't work in X or with remote
> > login.  Partly to do with pty's?
> >
> > Has anyone else seen this?  Should I file a bug?
>
> yes please.
>
> --
> MandrakeSoft         http://www.mandrakesoft.com/
>                                          --Chmouel

--
Mike Hahn
Senior Technician
Peregrine Metalforming, Inc.
Forming Technologies.
Voice: (810) 773-0800 Ext. 163
Fax  : (810) 773-0544
 [EMAIL PROTECTED]




Reply via email to