Edgar Simo-Serra

> Can I get a resource for what the order is in toolkit_* and what the names are in hparam? > > For the latter, if it is just the...

> w.r.t the trie, do we already have an implementation? Also, is there a standard file/set of files where such data structures are usually put, or can I put it...

How's the status on this?

OK, cool. No problem, I can look into it!

I've fixed almost everything in the [input branch](https://github.com/naev/naev/tree/input). One major issue is that, since the old strings have been removed, it won't be able to load old config files. Would...

OK, so the old way of doing it was we had `brief` and `name` field. So `brief="switchtab0", name="Switch Tab 0"`. You got rid of the brief field, so now it's...

First of all, please merge the `input` branch into your branch. It should merge cleanly except for the last commits you did. Second, that does not fix it, you're setting...

> To the first, very sorry, partway through that now. Are you merging the `input` branch not the `main` branch? I had fixed all the merge conflicts for you (you...

Honestly, since `find_key` is barely used (only in nlua_naev, and probably conf in the near future), it would be easier to just add it to `keybind_info` and do linear search...

OK, cool. > Correct me if I'm wrong, but our current loading is: {"accel": , ...} or something like that, right? Couldn't we load "accel" as 0 and store it...