paste-from-clipboard dosen't works on Cygwin platform
From: [EMAIL PROTECTED] To: bug-bash@gnu.org Subject: paste-from-clipboard dosen't works on Cygwin platform Configuration Information [Automatically generated, do not change]: Machine: i686 OS: cygwin Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i686-pc-cygwin' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -DRECYCLES_PIDS -I. -I/tmp/bash-3.1 -I/tmp/bash-3.1/include -I/tmp/bash-3.1/lib -O2 uname output: CYGWIN_NT-5.0 kirill-pc 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin Machine Type: i686-pc-cygwin Bash Version: 3.1 Patch Level: 17 Release Status: release Description: keyboard function paste-from-clipboard lost a bound to a key Repeat-By: I have a following line in the my .inputrc file: "\C-v": paste-from-clipboard After Bash has started the key is unbound: $ bind -p | grep -i clip # paste-from-clipboard (not bound) After "\C-x\C-r" keyboard sequence (re-read-init-file) it is bind the key to the function but only till next will typed. After any command or empty it is come to be unbound. Fix: smime.p7s Description: S/MIME Cryptographic Signature ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: paste-from-clipboard dosen't works on Cygwin platform
> Repeat-By: > I have a following line in the my .inputrc file: > "\C-v": paste-from-clipboard > > After Bash has started the key is unbound: > $ bind -p | grep -i clip > # paste-from-clipboard (not bound) > > After "\C-x\C-r" keyboard sequence (re-read-init-file) > it is bind the key to the function but only till next will > typed. After any command or empty > it is come to be unbound. > > > Fix: > This is expected behavior, and has been discussed on this list before. By default, terminals use Ctrl-V as the quoting character (see 'stty -a' and 'stty --help'). Readline 5.1 (and thus bash 3.1) added a new feature, bind-tty-special-characters, defaulted to on, which overrides key bindings in ~/.inputrc with those specified by the terminal. The solution, then, is to either turn this readline feature off (add "set bind-tty-special-characters off" to ~/.inputrc), or to tell your terminal to not bind Ctrl-V (add "stty lnext undef" to your ~/.bash_profile). If you like emacs bindings, where Ctrl-Q is the quoting character instead of Ctrl-V, you could do "stty lnext ^Q stop undef" instead. -- Eric Blake ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: bug of readline's vi keybinding function
Chet Ramey wrote: Hi, Recently, I want to add some keybindings for vi mode's vi-insert submode, I add the following lines into ~/.inputrc file: set editing-mode vi set keymap vi-insert "\C-A" : beginning-of-line "\C-B" : backward-char "\C-F" : forward-char "\C-E" : end-of-line ... ... In fact, I put almost all the emacs key bindings into vi-insert submode, since the default key bingdings of readline for vi-insert submode is too weak. By this way, I want to get the benefits from the two world. But it does not work, I have searched the web, but it is very difficult to find useful resource about vi mode in readline. It works fine when I try it. How exactly does it `not work'? Chet Hi, Chet Thanks for your reply. Here is my .inputrc file: === #"\e[3~": delete-char # this is actually equivalent to "\C-?": delete-char # VT "\e[1~": beginning-of-line "\e[4~": end-of-line # kvt "\e[H":beginning-of-line "\e[F":end-of-line # rxvt and konsole (i.e. the KDE-app...) "\e[7~":beginning-of-line "\e[8~":end-of-line set meta-flag on set convert-meta off set output-meta on # ignore case while completing set completion-ignore-case on # shut off the bell set bell-style none set editing-mode vi set visible-stats on set keymap vi-insert "\C-A" : beginning-of-line "\C-B" : backward-char "\C-E" : end-of-line "\C-F" : forward-char === After adding the keybindings, I open a new terminal(gnome Terminal 2.10.0), input some text and press Ctrl+B, it does not work. Am I doing something wrong? Linux vincent 2.6.10-5-386 #1 Tue Apr 5 12:12:40 UTC 2005 i686 GNU/Linux GNU bash, version 3.00.16(1)-release (i386-pc-linux-gnu) BR Vincent ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
