From: michael AT weiser DOT saale-net DOT de (Michael Weiser)
Subject: Re: B19.1:bind will not bind usinf the -f option.
18 Sep 1998 10:09:46 -0700
Message-ID: <36098a1c.9443408.cygnus.gnu-win32@mail.weiser.saale-net.de>
References: <915D4A5037A6D011957D006097198E47013DBAF3 AT goat DOT channelpoint DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
To: Alex Wykel <awykel AT channelpoint DOT com>
Cc: gnu-win32 AT cygnus DOT com

Hello Alex, you wrote:
>Upon trying to use the new binding nothing happened.  Investigating the 
>binding for the function showed that the new binding was never made.
bind works quite perfect for me. If I create some file containing

"\e[120~":	beginning-of-line

(yes, I know, it's bogus :) and then run 'bind -f bindings-file' I get

michael AT NARGOTHROND:/mnt/f/home/michael >bind -f bindings-file
michael AT NARGOTHROND:/mnt/f/home/michael >bind -q beginning-of-line
beginning-of-line can be invoked via "\C-a", "\e[120~", "\e[1~".
michael AT NARGOTHROND:/mnt/f/home/michael >

C-a and \e[1~ are predefined in my /etc/inputrc and automatically
bound on every start of bash. If you want to remove those already
existing definitions, you will have to use 'bind -r "\C-a"' for
example.

Hope that helps.
-- 
bye, Michael
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".