From: "erskine, michael" <michael.erskine@SERuk.com>
To: "'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: Re: AW: bash history not avail from arrow keys
Date: Sat, 31 Jul 1999 18:34:00 -0000 [thread overview]
Message-ID: <7154C38E706AD111B0670060977C7F8A0740F6@bilbo> (raw)
Message-ID: <19990731183400.AI73rEekaC4Wlzbo9lea0kGa9vTSNI5NYlIupWcEsGE@z> (raw)
Hi Tim,
Many thanks; that has shown me the way...
C-P & C-N do work (I didn't know about these gems!) and the arrow keys
on the numeric keypad work also (with num-lock off - I hadn't tried
them!). The PC-keyboard arrow keys still don't do anything but that's
not so bad because I am now equipped with C-p & C-n or the numeric
keypad.
You have all been most helpful - bless you.
Michael.
---------------------------
Tim wrote...
Hi,
A couple of things to check:
1. Do Control-P and Control-N work to retrieve Previous and Next
history commands?
2. Do your other arrow keys (left and right) work when editing the
command line? (I seem to remember that on my old notebook, the arrow
keys only worked when Num-Lock was turned off.)
Tim
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-07-31 18:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-22 2:22 erskine, michael [this message]
1999-07-31 18:34 ` erskine, michael
-- strict thread matches above, loose matches on Subject: below --
1999-07-22 15:10 Earnie Boyd
1999-07-31 18:34 ` Earnie Boyd
1999-07-22 8:26 erskine, michael
1999-07-31 18:34 ` erskine, michael
1999-07-22 3:48 Earnie Boyd
1999-07-31 18:34 ` Earnie Boyd
1999-07-22 0:43 erskine, michael
1999-07-22 1:47 ` Tim Davidson
1999-07-31 18:34 ` Tim Davidson
1999-07-31 18:34 ` erskine, michael
1999-07-22 0:29 Ahrens, Frank 6537 EPE-24
1999-07-31 18:34 ` Ahrens, Frank 6537 EPE-24
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=7154C38E706AD111B0670060977C7F8A0740F6@bilbo \
--to=michael.erskine@seruk.com \
--cc=cygwin@sourceware.cygnus.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).