`readline-set-option!` doesn't allow for setting keybindings

[jpellegrini]

After I made the PR I realized this:

stklos> (define-external readline-parse-and-bind ((line :string)) :entry-name "rl_parse_and_bind" :return-type :int)

stklos> (readline-parse-and-bind "Control-f: \"define\"")

Now when the user hits C-f readline automatically inserts the word define 😄

It is also possible to not just include text, but do actions like resetting the terminal, etc.

It also works for setting variables, but then one needs to use the command set:

stklos> (readline-parse-and-bind "set blink-matching-paren off")
stklos> (readline-parse-and-bind "set blink-matching-paren on")

But the PR I made actually hardcoded the set in readline-set-option, so one cannot change keybindings... Maybe we should change this?

1. Have a generic readline-config-line! instead of readline-set-option!?
2. Keep readline-set-option! and include readline-set-keybinding?
3. Keep readline-set-option! and include generic readline-config-line!?
4. Keep it as it is?

[egallesio]

Hi @jpellegrini

I had already added to my TODO list something like your [2] option (I thought to readline-bind!), while merging the PR. I prefer another primitive, because I'm not a fan of readline initialization language, and because it could conduct to allow file inclusion with $include, tests ...

This could also be useful to easily have a pretty UTF-8 lambda sign at the toplevel (for now I do it by modifying my keyboard and, with Wayland, it is very hacky).

If you want to implement it, it OK for me 😆.

[jpellegrini]

If you want to implement it, it OK for me 😆.

I'll try to do that, but it may take a while (personal issues are getting in the way)

[egallesio]

Hope everything will be OK for you soon @jpellegrini.
I'll implement it, no problem.