From: Chris <chrisl_ak@hotmail.com>
Subject: Re: Using control keys in bash shell within emacs
Date: Thu, 10 Oct 2002 16:16:24 -0000 [thread overview]
Message-ID: <Xns92A3540A32CCBchrislak@216.168.3.40> (raw)
In-Reply-To: t0fp9.32$ep1.64439@twister.nyroc.rr.com
on 10 Oct 2002, "Jeff Rancier" <jeff.rancier@softechnics.com> spake
thusly:
> Hi,
>
> I'm using cygwin bash, 2.05b, as my NTEmacs shell (GNU Emacs 21.2.1
> (i386-msvc-nt5.1.2600) of 2002-03-19 on buffy). Is there any way to
> have (e.g.) C-p, scroll through the history, instead of the default
> emacs behaviour of moving to the previous line in a buffer. I tried:
You could just use the normal Emacs history scrolling: M-p and M-n. I think
CTRL-up and CTRL-down work as well...
next prev parent reply other threads:[~2002-10-10 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 13:11 Using control keys in bash shell within emacs Jeff Rancier
2002-10-10 16:16 ` Chris [this message]
2002-10-11 4:46 ` Knut Forkalsrud
2002-10-11 10:14 ` FRC
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Xns92A3540A32CCBchrislak@216.168.3.40 \
--to=chrisl_ak@hotmail.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).