From: Evgeny Roubinchtein <zhenya1007@gmail.com>
To: Marshall <marshall@logical.net>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Configure utop to use rlwrap/emacs history keys?
Date: Fri, 14 Apr 2017 09:46:49 -0400 [thread overview]
Message-ID: <CAGYXaSaCX2JD1He9MbOUwMUDt96fGqYJwg85wpJ-PZzsihpaAA@mail.gmail.com> (raw)
In-Reply-To: <ABE2E4FE-BA2B-4408-B3A9-DE6B3137690D@logical.net>
[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]
I agree with your reading of lambda-term-inputrc man page, but I disagree
with your reading of the output of lambda-term-actions. I think the
following stanza should give you the effect you want:
[read-line]
C-p: history-next
C-n: history-prev
--
Best,
Zhenya
On Fri, Apr 14, 2017 at 2:40 AM, Marshall <marshall@logical.net> wrote:
> Newbie question:
>
> On OSX 10.11, I would like to configure utop so that Ctrl-P moves to the
> previously entered line of code, and so that Ctrl-N moves back down toward
> the most recent line. According to what ‘man lambda-term-inputrc' and
> ‘lambda-term-actions’ say, it seems to me that I ought to be able to get
> this behavior by putting the following in .lambda-term-inputrc in my home
> directory:
>
> [read-line]
> C-p: next-line
> C-n: prev-line
>
> However, this configuration to have no effect. I can move up and down
> through command history using the arrow keys, as I could without the rc
> file, Ctrl-P and Ctrl-N still do nothing.
>
> Thanks very much-
>
> Marshall
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
[-- Attachment #2: Type: text/html, Size: 2035 bytes --]
next prev parent reply other threads:[~2017-04-14 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 6:40 Marshall
2017-04-14 13:25 ` Francois BERENGER
2017-04-14 13:46 ` Evgeny Roubinchtein [this message]
2017-04-14 15:06 ` Marshall
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=CAGYXaSaCX2JD1He9MbOUwMUDt96fGqYJwg85wpJ-PZzsihpaAA@mail.gmail.com \
--to=zhenya1007@gmail.com \
--cc=caml-list@inria.fr \
--cc=marshall@logical.net \
/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 NNTP newsgroup(s).