Axel Liljencrantz <[EMAIL PROTECTED]> writes: > > This is usually caused by the terminal not doing what the terminfo > database says it will.
> After doing that, try pressing one of the buttons that don't work, > e.g. the up arrow. The sequence of characters generated from this can > then be bound to the correct action. This is done using the fish > builtin called bind. It accepts two arguments, the sequence and the > action. For example, if the sequence for up was 1b 5b 41 (in > hexadecimal) we might use this command: > > bind \x1b\x5b\x41 up-or-search Hi Alex, I built and ran key_reader but running bind did not make the up arrow work. Here is the transcript: [EMAIL PROTECTED] ~/f/fish-1.23.0> ./key_reader.exe dec: 27 hex: 1b dec: 91 hex: 5b char: [ dec: 65 hex: 41 char: A fish: Job 1, './key_reader.exe ' terminated by signal SIGINT (Quit request from job control (^C)) [EMAIL PROTECTED] ~/f/fish-1.23.0> bind \x1b\x5b\x41 up-or-search [EMAIL PROTECTED] ~/f/fish-1.23.0> ÿ fish: Unknown command 'ÿ' [EMAIL PROTECTED] ~/f/fish-1.23.0> After looking at this a little more, I am pretty sure that bind already has up-or-search correctly defined. However something is going wrong with the escape key. Just typing the escape key by itself generates the y key with the two dots and none of the fish escape sequences seem to be working. If I can be of help in debugging this I'm happy to work with you. On the other hand I don't want to hassle you so any response you send is appreciated but I understand if you want to drop this at some point. - Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
