Invalid array subscript (single backslash) causes assertion failure

Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale'

Re: Memory leak when catting(/sedding/...) large binary files with backticks

Chet Ramey wrote: [EMAIL PROTECTED] wrote: Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'

Re: builtin printf not printing unicode characters?

pk wrote: The man page says that bash builtin printf supports the standard printf(1) formats. But it seems that \u is not working: $ /usr/bin/printf '\u212b\n' Å $ printf '\u212b\n' \u212b Am I doing something wrong here? The `\u' format string escape is not standard. I will consider it

Re: builtin printf not printing unicode characters?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Chet Ramey on 5/10/2008 8:16 PM: | The `\u' format string escape is not standard. I will consider it for a | future enhancement. You may also be interested in this recent thread on coreutils' printf and \u:

Re: spaces in the shebang interpreter path

On Sun, May 11, 2008 at 02:01:29PM -0400, Paul Jarc wrote: Felix Schwarz [EMAIL PROTECTED] wrote: I'm not able to specify an interpreter in a shebang line if the path to this interpreter contains spaces. It's actually the kernel that interprets that line, not bash. The

PATH value doesn't get updated

I put this in my .bash_profile: PATH=$PATH:/opt/lampp/bin export PATH but when I echo $PATH it doesn't include the /opt/lampp/bin. -- View this message in context: http://www.nabble.com/PATH-value-doesn%27t-get-updated-tp17189469p17189469.html Sent from the Gnu - Bash mailing list archive at

Re: PATH value doesn't get updated

carlwenrich wrote: I put this in my .bash_profile: PATH=$PATH:/opt/lampp/bin export PATH but when I echo $PATH it doesn't include the /opt/lampp/bin. The .bash_profile is sourced by bash when it is invoked as an interactive login shell. Therefore you would need to log in after having

Re: PATH value doesn't get updated

Yes. I (1) made the change to .bash_profile, then (2) restarted the machine, then (3) logged in again. When I echo $PATH the /opt/lampp/bin is not included. Bob Proulx [EMAIL PROTECTED] wrote: carlwenrich wrote: I put this in my .bash_profile: PATH=$PATH:/opt/lampp/bin export PATH but

Re: PATH value doesn't get updated

Carl Wenrich wrote: Bob Proulx wrote: Did you log in after having made that change? Was bash invoked as an interactive login shell so that it would read that file? echo $0 echo $- Yes. I (1) made the change to .bash_profile, then (2) restarted the machine, then (3) logged in

Re: PATH value doesn't get updated

echo $0 gives me bash echo $- gives me himBH Bob Proulx [EMAIL PROTECTED] wrote: Carl Wenrich wrote: Bob Proulx wrote: Did you log in after having made that change? Was bash invoked as an interactive login shell so that it would read that file? echo $0 echo $- Yes. I (1) made

Re: PATH value doesn't get updated

Carl Wenrich wrote: echo $0 gives me bash echo $- gives me himBH Then bash hasn't been invoked as a login shell and therefore isn't instructed to source the .bash_profile. If it is not a login shell then to suggest improvements it would be necessary to know the type of system you are using

Re: PATH value doesn't get updated

I just log into the box that appears on the standard ubuntu startup. I enter my username and password, then the desktop comes up. I see now that the .bash_profile isn't being sourced (I thought it was according to what I've been able to pick up on the web). If I source it manually, the $PATH