bash ignoring .inputrc (or am I dumb)
So I don't really like posting this to a bugs list, since I have no idea if this is a bug, but I tried this on a couple of general UNIX related lists, and haven't had any luck. I have ^W bound to "backward-kill-word" in my .inputrc. On FreeBSD, Red Hat Linux, FC4, and anything else with a bash version > 3, I can't seem to get this to work as I expect. I've tried adding other changes to .inputrc, and they don't seem to be read either. I tried setting $INPUTRC to $HOME/.inputrc (even though that's the default), and that doesn't seem to work either. I've tried both: "\C-w": backward-kill-word and ^W: backward-kill-word (with a literal ^W) FreeBSD 5.4: $ echo $BASH_VERSION 3.00.16(1)-release $ uname -srm FreeBSD 5.4-RELEASE-p7 i386 Fedora Core 5: $ echo $BASH_VERSION 3.1.7(1)-release $ uname -srm Linux 2.6.15-1.2054_FC5 i686 I've used this on machines running bash v 2.05 and thereabouts w/ no problems. w ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: bash ignoring .inputrc (or am I dumb)
Arrgh... Ok, so the good news is that I checked the archives; the bad news is that I checked them after reading: http://lists.gnu.org/archive/html/bug-bash/2005-08/msg3.html trying ^x ^r does indeed make it work for that line. jazz:$ stty -a speed 38400 baud; rows 38; columns 80; line = 140; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 = ; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; I would still like to know if there's a way to bind ^W to backward-kill-word within bash, so if anyone has suggestions, I'd appreciate them. w ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
pattern matching: range expression
Configuration Information [Automatically generated, do not change]: Machine: i386 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu' -DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H -I. -I../bash -I../bash/include -I../bash/lib -g -O2 uname output: Linux Saint-Saens 2.6.8-2-386 #1 Tue Aug 16 12:46:35 UTC 2005 i686 GNU/Linux Machine Type: i386-pc-linux-gnu Bash Version: 2.05b Patch Level: 0 Release Status: release Description: Problems with range expressions like [A-Z] e.g. ls [A-Z]* should yield in all names starting with capital letters. Does not work! I get >>all<< names! Repeat-By: ls [A-Z]* in a directory which contains names which start with both upper and lower characters. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: bash ignoring .inputrc (or am I dumb)
William Yardley <[EMAIL PROTECTED]> wrote: > I would still like to know if there's a way to bind ^W to > backward-kill-word within bash, so if anyone has suggestions, I'd > appreciate them. Check out the "bind" builtin command in the man page or "help bind". paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: pattern matching: range expression
Wolf-Rainer Novender <[EMAIL PROTECTED]> wrote: > e.g. ls [A-Z]* should yield in all names starting with capital letters. > Does not work! I get >>all<< names! http://www.gnu.org/software/coreutils/faq/#Sort-does-not-sort-in-normal-order_0021 paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: bash ignoring .inputrc (or am I dumb)
> I have ^W bound to "backward-kill-word" in my .inputrc. On FreeBSD, Red > Hat Linux, FC4, and anything else with a bash version > 3, I can't seem > to get this to work as I expect. I've tried adding other changes to > .inputrc, and they don't seem to be read either. I tried setting > $INPUTRC to $HOME/.inputrc (even though that's the default), and that > doesn't seem to work either. Bash picks up bindings from the stty special characters. On bash-3.1, that behavior is optional: look at the `bind-tty-special-chars' readline variable. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live Strong. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.case.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: bash ignoring .inputrc (or am I dumb)
On Thu, Mar 30, 2006 at 11:13:44AM -0500, Paul Jarc wrote: > William Yardley <[EMAIL PROTECTED]> wrote: > > I would still like to know if there's a way to bind ^W to > > backward-kill-word within bash, so if anyone has suggestions, I'd > > appreciate them. > Check out the "bind" builtin command in the man page or "help bind". So, forgive me if I'm dense, but: bind '"\C-w": backward-kill-word' ? This doesn't seem to work w/ bash 3.00.x; with other versions, it works just the same as putting it in .inputrc. So I don't think this really fixes the "problem" w/ bindings defined by the system. On Thu, Mar 30, 2006 at 11:17:32AM -0500, Chet Ramey wrote: > Bash picks up bindings from the stty special characters. On bash-3.1, > that behavior is optional: look at the `bind-tty-special-chars' > readline variable. set bind-tty-special-chars off in .inputrc works for me w/ 3.1 - thanks (Do I need to do any conditional tests on bash version? It doesn't seem to cause any errors with older versions of Readline). Is there any "fix" (even a dumb one) within bash 3.00.x? I'm likely to be using the vendor supplied bash for a while on a lot of systems (RHEL 4, for instance), and don't particularly want to futz with installing a different version. w ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: bash ignoring .inputrc (or am I dumb)
William Yardley wrote: > On Thu, Mar 30, 2006 at 11:17:32AM -0500, Chet Ramey wrote: > >> Bash picks up bindings from the stty special characters. On bash-3.1, >> that behavior is optional: look at the `bind-tty-special-chars' >> readline variable. > > set bind-tty-special-chars off in .inputrc works for me w/ 3.1 - thanks > (Do I need to do any conditional tests on bash version? It doesn't seem > to cause any errors with older versions of Readline). > > Is there any "fix" (even a dumb one) within bash 3.00.x? I'm likely to > be using the vendor supplied bash for a while on a lot of systems (RHEL > 4, for instance), and don't particularly want to futz with installing a > different version. You don't need any conditionals -- readline ignores unrecognized variables. There is, unfortunately in retrospect, no workaround for 3.0. It is just not configurable in that version. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
