caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Marshall <marshall@logical.net>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Configure utop to use rlwrap/emacs history keys?
Date: Fri, 14 Apr 2017 10:06:47 -0500	[thread overview]
Message-ID: <D69B4C7D-5C70-4F92-A622-2CF765DFDABC@logical.net> (raw)
In-Reply-To: <CAGYXaSaCX2JD1He9MbOUwMUDt96fGqYJwg85wpJ-PZzsihpaAA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2426 bytes --]

Thanks for all of the replies.

Zhenya, history-next/prev was the key.  Excellent!  Now I can work happily.  Thanks very much.

I noticed that caml-list emails have reply-to set to the person who posted.  Is it the convention to reply off-list for most followups of this kind?

(Francois, I checked and ^P and ^N actually are the Emacs previous/next line keys in my vanilla Emacs—it wasn’t just my fingers that thought so!  Meta-P and Meta-N are unbound.  (I have to use the uber-traditional Esc- prefix to get Meta, as Alt- and Apple- do other things by default for me.))

(Tao: Yeah, lately Apple sometimes seems to have a “if it’s not broken and is better than anything else, let’s mess it up” attitude.  I think the X is supposed to be Roman numeral 10, so maybe Apple is planning to increment X and doesn’t like "OSXI".)

Marshall

> On Apr 14, 2017, at 8:46 AM, Evgeny Roubinchtein <zhenya1007@gmail.com> wrote:
> 
> 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 <mailto: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 <https://sympa.inria.fr/sympa/arc/caml-list>
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners <http://groups.yahoo.com/group/ocaml_beginners>
> Bug reports: http://caml.inria.fr/bin/caml-bugs <http://caml.inria.fr/bin/caml-bugs>


[-- Attachment #2: Type: text/html, Size: 4146 bytes --]

      reply	other threads:[~2017-04-14 15:07 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
2017-04-14 15:06   ` Marshall [this message]

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=D69B4C7D-5C70-4F92-A622-2CF765DFDABC@logical.net \
    --to=marshall@logical.net \
    --cc=caml-list@inria.fr \
    /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).