wait: mention PID must be a child of this shell
$ help wait doesn't mention that PID must be a child of this shell. Nor does it advise how to wait if PID is not a child of this shell. User wanted to do noffle --f & (wait $!; noffle -f) & for better or worse. User forced to use (noffle -f; noffle -f)& ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: wait: mention PID must be a child of this shell
Dan Jacobson wrote: > $ help wait > doesn't mention that PID must be a child of this shell. > Nor does it advise how to wait if PID is not a child of this shell. There's no way to do this, you know. Since the underlying plumbing is not there, there's no need to mention the limitation. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live...Laugh...Love 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: Clearing window (^L) messes up command line
[EMAIL PROTECTED] wrote: > 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.0 > -I/tmp/bash-3.0/include -I/tmp/bash-3.0/lib -O2 > uname output: CYGWIN_NT-5.0 PN100-01-1-123s 1.5.17(0.129/4/2) 2005-05-25 > 19:38 i686 unknown unknown Cygwin > Machine Type: i686-pc-cygwin > > Bash Version: 3.0 > Patch Level: 16 > Release Status: release > > Description: > > Typing in a command (without hitting ), and then clearing the window > with ^L results in extra characters being added to the command line. > This may be the result of bash not properly taking into account escape > sequences in the prompt. I cannot reproduce this, though I do not run cygwin. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live...Laugh...Love 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 doesn't compile when configured with --disable-bang-history
> Machine Type: i686-pc-linux-gnu > > Bash Version: 3.0 > Patch Level: 0 > Release Status: release > > Description: > It is not possible to selectively disable the history expansion with >--disable-bang-history Fixed, thanks. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live...Laugh...Love 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 3 and $HOME abbreviated with a tilde.
J.O. Aho wrote:
>
> Got a bit irritated when updating my Gentoo boxes to use bash 3.00.16,
> the \W and \w options for the prompt now replaces the home directory
> name to tilde, I hope I'm not the only one who wants to see the home
> directory name instead of the tilde.
>
> Wouldn't it be possible to see options \U and \u (just a suggestion)
> which behaives as \W and \w used to do under 2.05.
I'd rather not do that. It's trivial to emulate the 2.05 behavior using
something like ${PWD##/*/}. It's not quite as easy to emulate the 3.0
behavior using shell expansions.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
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: ESC t not ready for Chinese
Dan Jacobson wrote: > If I put the cursor between the last two items, > $ search 鼓山 福州 > and type ESC t, I get > $ s 福州 鼓山earch > Whereas in real emacs, I correctly get > $ search 福州 鼓山 I did some work after 3.0 was released to make forward-word and backward-word work correctly with multibyte characters. As a result, transpose-words should work correctly, since it's built atop those functions. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live...Laugh...Love 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
Part 2 follow-up
I realized I didn't send you this in my first email. From: root To: bug-bash@gnu.org Subject: [50 character or so descriptive subject here (for reference)] Configuration Information [Automatically generated, do not change]: Machine: powerpc OS: aix5.2.0.0 Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='powerpc' -DCONF_OSTYPE='aix5.2.0.0' -D CONF_MACHTYPE='powerpc-ibm-aix5.2.0.0' -DCONF_VENDOR='ibm' -DLOCALEDIR='/usr/local2/share/loc ale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -g -O2 uname output: AIX tmupdb1r 2 5 00C4598E4C00 Machine Type: powerpc-ibm-aix5.2.0.0 Bash Version: 3.0 Patch Level: 0 Release Status: release Description: [All of the colors do not work, from /etc/DIR_COLORS.] Repeat-By: [Repeatable on all IBM AIX servers (I have 16, running different versions of AIX).] Ray McCaffity Midrange Cluster and Database 651.962.1063 [EMAIL PROTECTED] -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. == DIR_COLORS Description: Binary data ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
directory colors on AIX
bash --version GNU bash, version 3.00.0(1)-release (powerpc-ibm-aix5.2.0.0) Copyright (C) 2004 Free Software Foundation, Inc. I am running AIX 5.2. I copied the /etc/DIR_COLORS from a linux box, and added the alias ls='ls --color=auto' to my .bashrc file. It mostly seems to work. The colors for the directories, links and executables are all OK. But my tar's and gz's and bz2's are not red. It's almost like everything here... NORMAL 00 # global default, although everything should be something. FILE 00 # normal file DIR 01;34 # directory LINK 01;36 # symbolic link FIFO 40;33 # pipe SOCK 01;35 # socket BLK 40;33;01# block device driver CHR 40;33;01# character device driver ORPHAN 01;05;37;41 # orphaned syminks MISSING 01;05;37;41 # ... and the files they point to # This is for files with execute permission: EXEC 01;32 is the part that works. while this part... .tar 01;31 # archives or compressed (bright red) .tar 31 # archives or compressed (bright red) .tgz 01;31 .arj 01;31 .taz 01;31 .lzh 01;31 .zip 01;31 .z 01;31 .Z 01;31 .gz 01;31 .bz2 01;31 .bz2 31 .bz 01;31 .tz 01;31 .doesn't work. I have tried downloading bash from several freeware sites already pre-compiled. I have even compiled my own. It's great. But just wonder why all the colors don't work. A minor annoyance, true. But maybe you have an easy answer. I have also used several different SSH and Telnet clients, (the colors are correct when I log onto Linux servers). Ray McCaffity Midrange Cluster and Database 651.962.1063 [EMAIL PROTECTED] -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. == ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
bug in bash handling of PS1 prompt
Configuration Information [Automatically generated, do not change]: Machine: i386 OS: linux-gnu Compiler: i386-redhat-linux-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -D_GNU_SOURCE -O2 -march=i386 -mcpu=i686 -g uname output: Linux skywalker.ca.boeing.com 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 GNU/Linux Machine Type: i386-redhat-linux-gnu Bash Version: 2.05b Patch Level: 0 Release Status: release Description: [Detailed description of the problem, suggestion, or complaint.] Not sure if this was meant as a bug or feature, but I think it is a bug in bash. When assigning to PS1 to change the prompt, bash appears to append any new value to the initial default value, rather than to replace it. The human user cannot see the original elements in the prompt. Although not disturbing visually, bash sends a lot of unnecessary characters out at each prompt. If you use "script" or "expect" with logging turned on, the log will show that each prompt contains the original and new values of PS1. Unsetting PS1 and then setting PS1 does not get around the problem. Changing PS1 does replace the last PS1 assignment the user made, but does not remove the initial value. Repeat-By: The bash session shown below was captured with "script", and then post-processed with "cat -v", and shows the bug in bash's handling of PS1. The first prompt shown below indicates that the PS1 set in the /etc/bashrc file was added to the default prompt. The "script" command was run on RedHat 9.0. Stan Tazuma Boeing [EMAIL PROTECTED] Script started on Wed 22 Jun 2005 02:51:50 PM PDT ^[]0;[EMAIL PROTECTED]:~/bugs/[EMAIL PROTECTED] bash-prompt]$ date^M Wed Jun 22 14:51:53 PDT 2005^M ^[]0;[EMAIL PROTECTED]:~/bugs/[EMAIL PROTECTED] bash-prompt]$ echo $BASH_VERSION^M 2.05b.0(1)-release^M ^[]0;[EMAIL PROTECTED]:~/bugs/[EMAIL PROTECTED] bash-prompt]$ echo "$PS1"^M [EMAIL PROTECTED] \W]\$ ^M ^[]0;[EMAIL PROTECTED]:~/bugs/[EMAIL PROTECTED] bash-prompt]$ PS1='hello> '^M ^[]0;[EMAIL PROTECTED]:~/bugs/bash-prompt^Ghello> date^M Wed Jun 22 14:52:20 PDT 2005^M ^[]0;[EMAIL PROTECTED]:~/bugs/bash-prompt^Ghello> PS1=''^M ^[]0;[EMAIL PROTECTED]:~/bugs/bash-prompt^Gdate^M Wed Jun 22 14:52:25 PDT 2005^M ^[]0;[EMAIL PROTECTED]:~/bugs/bash-prompt^G Script done on Wed 22 Jun 2005 02:52:29 PM PDT ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
