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 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 > 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