zsh-workers
 help / color / mirror / code / Atom feed
From: Andy Wick <awick@actor.cs.vt.edu>
To: zsh-workers@math.gatech.edu
Subject: Re: Bindkey problem on Solaris 2.6 with zefram4
Date: Fri, 10 Apr 1998 18:08:24 -0400	[thread overview]
Message-ID: <19980410180824.53147@actor.cs.vt.edu> (raw)
In-Reply-To: <m267khuz44.fsf@dep1.fciencias.unam.mx>; from Francisco Solsona on Fri, Apr 10, 1998 at 04:48:43PM -0500

On Fri, Apr 10, 1998 at 04:48:43PM -0500, Francisco Solsona wrote:
> Andy Wick <awick@actor.cs.vt.edu> writes:
> 
> > I am upgrading from 3.0.5 to 3.1.2-zefram4 so sorry if I missed something obvious.  
> > 
> > The arrow keys just don't work.  I tried doing a 
> >    zsh -f
> >    bindkey -d
> > and that does fix them.  I tried doing what I do for 3.0.5
> 	   ^^^^^^^^
> 
> 	You mean "does not" fix them, right? Anyway, maybe it has something 
> to do with Solaris 2.6, we're using 3.1.2-zefram4 on Solaris 2.5 and Linux
> 2.0.32 with not a single problem.

Sorry you are right I meant does NOT!


> 	I use this bindkey in mi .zshrc,
> 
> 	bindkey -me
> 
> and the arrow keys have been working as usual.

Yes this does work!  This gave me an idea.  Arrows work FINE
no matter how I do it *IF* I use up-arrow-or-history (which is what -me does).
But if I use my up-arrow-or-search then it doesn't work.  I did just 
a straight ./configure so I am not use modules or anything.  Do I need to
for the up-arrow-or-search to work?  

Thanks for getting me closer!!!

Thanks,
Andy
-- 
awick@vt.edu                                    Andy Wick
awick@purple.org                              Virginia Tech


  reply	other threads:[~1998-04-10 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-10 21:14 Andy Wick
1998-04-10 21:48 ` Francisco Solsona
1998-04-10 22:08   ` Andy Wick [this message]
1998-04-10 22:23 ` Mark Borges
1998-04-14  9:32   ` Andrew Main

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19980410180824.53147@actor.cs.vt.edu \
    --to=awick@actor.cs.vt.edu \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).