Re: [vox-tech] vi key bindings, readline and bash
Peter Jay Salzman wrote: chuck, is your libreadline 4.2 or 4.3?every 4.2 system i've tried, it works. it doesn't seem to work on 4.3. I locate'd this file: /lib/libreadline.so.4.2 so I guess it's 4.2... Could it be something to do with $TERM ? Mine's set to xterm, but iirc sometimes people use linux or some such. ? ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] vi key bindings, readline and bash
begin Charles Polisher [EMAIL PROTECTED] Peter Jay Salzman wrote: chuck, is your libreadline 4.2 or 4.3?every 4.2 system i've tried, it works. it doesn't seem to work on 4.3. I locate'd this file: /lib/libreadline.so.4.2 so I guess it's 4.2... Could it be something to do with $TERM ? Mine's set to xterm, but iirc sometimes people use linux or some such. ? i used to set mine to linux, but switched over to xterm awhile ago. hrmmm... i think perhpas it's time to post a question to bug-readline. thanks, chuck. i appreciate you putting up with my questions. :) pete -- Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] vi key bindings, readline and bash
Peter Jay Salzman wrote: begin Charles Polisher [EMAIL PROTECTED] Peter Jay Salzman wrote: chuck, is your libreadline 4.2 or 4.3?every 4.2 system i've tried, it works. it doesn't seem to work on 4.3. I locate'd this file: /lib/libreadline.so.4.2 so I guess it's 4.2... Could it be something to do with $TERM ? Mine's set to xterm, but iirc sometimes people use linux or some such. ? i used to set mine to linux, but switched over to xterm awhile ago. hrmmm... i think perhpas it's time to post a question to bug-readline. thanks, chuck. i appreciate you putting up with my questions. :) I'm always pleased if I can help, Chuck -- Object-oriented programming is an exceptionally bad idea which could only have originated in California.--Edsger Dijkstra ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] vi key bindings, readline and bash
Tim Riley wrote: Peter Jay Salzman wrote: if someone wants to do me a favor... 1. download bash_bindings.txt from vh224401.truman.edu/~dbindner/mirror 2. source it (source bash_bindings.txt) 3. hit the up arrow key 4. make sure your last history item is pulled up This doesn't work right anymore; right arrow or left arrow then up arrow makes it work. 5. make sure the cursor is at the END of the history line. The cursor is at the beginning. it's a set of key bindings that make readline's vi-style input more friendly. for instance, history is just up arrow rather than escape up arrow. My history is just up arrow by default. it works for me, except step 5. the cursor is placed at the BEGINNING of the line for me, despite the fact that: bind -m vi-command '[A: kA' that A should be placing the cursor at the END of the line and putting me in insert mode. does it work for anybody? Not here. SuSE does the right thing as-is; this is from /etc/inputrc : $if mode=vi set editing-mode vi set keymap vi $endif and the environment has INPUTRC set to /etc/inputrc, but that can be overridden with ~/.inputrc (bash refman p.82) -- Owning a power guillotine means never having to say you're sorry. ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] vi key bindings, readline and bash
begin Charles Polisher [EMAIL PROTECTED] Tim Riley wrote: Peter Jay Salzman wrote: if someone wants to do me a favor... 1. download bash_bindings.txt from vh224401.truman.edu/~dbindner/mirror 2. source it (source bash_bindings.txt) 3. hit the up arrow key 4. make sure your last history item is pulled up This doesn't work right anymore; right arrow or left arrow then up arrow makes it work. 5. make sure the cursor is at the END of the history line. The cursor is at the beginning. it's a set of key bindings that make readline's vi-style input more friendly. for instance, history is just up arrow rather than escape up arrow. My history is just up arrow by default. it works for me, except step 5. the cursor is placed at the BEGINNING of the line for me, despite the fact that: bind -m vi-command '[A: kA' that A should be placing the cursor at the END of the line and putting me in insert mode. does it work for anybody? Not here. SuSE does the right thing as-is; this is from /etc/inputrc : $if mode=vi set editing-mode vi set keymap vi $endif and the environment has INPUTRC set to /etc/inputrc, but that can be overridden with ~/.inputrc (bash refman p.82) hi chuck, i'm not sure how that can possibly be; seems really impossible. just to make absolutely sure, beyond a shadow of a doubt, can you tell me what you mean by does the right thing? there needs to be more than this, unless suse started hacking on readline source code... thanks! pete -- Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] vi key bindings, readline and bash
Peter Jay Salzman wrote: does it work for anybody? Not here. SuSE does the right thing as-is; this is from /etc/inputrc : $if mode=vi set editing-mode vi set keymap vi $endif and the environment has INPUTRC set to /etc/inputrc, but that can be overridden with ~/.inputrc (bash refman p.82) hi chuck, i'm not sure how that can possibly be; seems really impossible. just to make absolutely sure, beyond a shadow of a doubt, can you tell me what you mean by does the right thing? there needs to be more than this, unless suse started hacking on readline source code... Does the right thing: From an ordinary bash prompt, with a typical U.S. installation of SuSE Linux 8.0, inside a standard xterm, logged in as an ordinary user, with no further customizations of the shell, press the up-arrow key. The shell displays the most recently typed command from the shell history, without moving the cursor to a different line, but positioning the cursor just beyond the last character of the command. At this point, pressing the Enter key causes that displayed command to execute. Additional up-arrow key presses will go further back in the shell history, while down-arrow replaces the displayed command with more recent commands. set keymap vi is part of the standard Gnu bash distribution, as documented in the Bash Reference Manual, 2.5a-th ed., 11/2001. Thusly speaketh the man page (excuse please the fleckths of thspittle on the thscreen, I blame the dentithst): keymap (emacs) Set the current readline keymap. The set of valid keymap names is emacs, emacs-standard, emacs-meta, emacs-ctlx, vi, vi-command, and vi-insert. vi is equivalent to vi-command; emacs is equivalent to emacs-standard. The default value is emacs; the value of editing-mode also affects the default keymap. That (emacs) in the first line gives the default value. Also, under man 3 readline, the section on default key bindings lists the complete VI Mode bindings. Werner Fink is credited with the inputrc file, which also has these lines: $if term=xterm \e[5;5~: history-search-backward \e[6;5~: history-search-forward $endif \e[C: forward-char \e[D: backward-char \e[A: previous-history \e[B: next-history Maybe that's the magic you've been looking for? -- Violence is the last resort of the incompetent. The competent, of course, make it their *first* resort. ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] vi key bindings, readline and bash
begin Charles Polisher [EMAIL PROTECTED] Peter Jay Salzman wrote: does it work for anybody? Not here. SuSE does the right thing as-is; this is from /etc/inputrc : $if mode=vi set editing-mode vi set keymap vi $endif and the environment has INPUTRC set to /etc/inputrc, but that can be overridden with ~/.inputrc (bash refman p.82) hi chuck, i'm not sure how that can possibly be; seems really impossible. just to make absolutely sure, beyond a shadow of a doubt, can you tell me what you mean by does the right thing? there needs to be more than this, unless suse started hacking on readline source code... Does the right thing: From an ordinary bash prompt, with a typical U.S. installation of SuSE Linux 8.0, inside a standard xterm, logged in as an ordinary user, with no further customizations of the shell, press the up-arrow key. The shell displays the most recently typed command from the shell history, without moving the cursor to a different line, but positioning the cursor just beyond the last character of the command. At this point, pressing the Enter key causes that displayed command to execute. Additional up-arrow key presses will go further back in the shell history, while down-arrow replaces the displayed command with more recent commands. set keymap vi is part of the standard Gnu bash distribution, as documented in the Bash Reference Manual, 2.5a-th ed., 11/2001. Thusly speaketh the man page (excuse please the fleckths of thspittle on the thscreen, I blame the dentithst): keymap (emacs) Set the current readline keymap. The set of valid keymap names is emacs, emacs-standard, emacs-meta, emacs-ctlx, vi, vi-command, and vi-insert. vi is equivalent to vi-command; emacs is equivalent to emacs-standard. The default value is emacs; the value of editing-mode also affects the default keymap. That (emacs) in the first line gives the default value. Also, under man 3 readline, the section on default key bindings lists the complete VI Mode bindings. Werner Fink is credited with the inputrc file, which also has these lines: $if term=xterm \e[5;5~: history-search-backward \e[6;5~: history-search-forward $endif \e[C: forward-char \e[D: backward-char \e[A: previous-history \e[B: next-history Maybe that's the magic you've been looking for? rats. so it doesn't work on 2 debian testing systems. it DOES work on a debian woody system it works on a redhat 7.3 system (i just checked) it works on your suse system hrm. i'm starting to think maybe this is a bug in debian/testing readline bash.:-/ when i get back home, i'll try using the inputrc sitting on the redhat 7.3 machine that it worked on. pete -- Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] vi key bindings, readline and bash
chuck, is your libreadline 4.2 or 4.3?every 4.2 system i've tried, it works. it doesn't seem to work on 4.3. pete begin Charles Polisher [EMAIL PROTECTED] Peter Jay Salzman wrote: does it work for anybody? Not here. SuSE does the right thing as-is; this is from /etc/inputrc : (snip) ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
