Hi Jamie,
do you start the ReadlineTest from the makefile? It will then read a private
init-file from src/test/tinputrc, which cancels all initialization from
~/.inputrc. Try changing src/test/tinputrc, or start ReadlineTest without
arguments (then it won't read the tinputrc).
Maybe this helps. Please let me know your results.
Bernhard
> Hi. I've been trying to use the java readline package in a utility I'm
> writing. I'm having some trouble with the EMACS/vi editing modes. I'm using
> the ReadlineTest class that was included with the download.
>
> If I run the program without a ~/.inputrc file, it runs it EMACS mode as
> default. This works well. Also, if I want to switch to vi editing mode, I
> press ESC, and then Ctrl+j and I can use either vi or emacs (ESC-k or arrow
> keys). If I create the ~/.inputrc file with the line set editing-mode emacs
> , I get the same behaviour.
>
> The strange behaviour happens if I change ~/.inputrc to read set
> editing-mode vi . If I run java ReadlineTest then, EMACS doesn't work, vi
> doesn't work and the ESC-Ctrl-j keystroke doesn't switch.
>
> Many of my users already have the vi line in their ~/.inputrc file (for
> other programs), so command-line history will not work in my app for them.
>
> Does anyone know a way of making the app start up correctly in vi mode?
|