Re: How cd to a directory with special characters like environment\<\-?

On Thu, 8 Apr 2010, Peng Yu wrote: > I make the following directory and try to cd to it. But I can't. Could > you let me know what is the correct way of doing so? > > $ mkdir environment\<\- > $ cd environmen\<\- > -bash: cd: environmen<-: No such file or directory Try using the same spelling

Re: How cd to a directory with special characters like environment\<\-?

On Thu, Apr 8, 2010 at 4:58 PM, Peng Yu wrote: > I make the following directory and try to cd to it. But I can't. Could > you let me know what is the correct way of doing so? > > $ mkdir environment\<\- > $ cd environmen\<\- > -bash: cd: environmen<-: No such file or directory Never mind. I get i

How cd to a directory with special characters like environment\<\-?

I make the following directory and try to cd to it. But I can't. Could you let me know what is the correct way of doing so? $ mkdir environment\<\- $ cd environmen\<\- -bash: cd: environmen<-: No such file or directory -- Regards, Peng

Re: bash exit command should be unconditional

Greg Wooledge wrote: > Bob Proulx wrote: > > Greg Wooledge wrote: > > > Migrating FROM something that used Korn shell, I presume? Why not > > > just install Korn shell and use #!/bin/ksh on your scripts, if you need > > > to rely on Korn shell features? > > > When I read this I was torn about sug

Re: bash exit command should be unconditional

On Thu, Apr 08, 2010 at 10:07:32AM -0600, Bob Proulx wrote: > Greg Wooledge wrote: > > Migrating FROM something that used Korn shell, I presume? Why not > > just install Korn shell and use #!/bin/ksh on your scripts, if you need > > to rely on Korn shell features? > When I read this I was torn ab

Re: bash exit command should be unconditional

Greg Wooledge wrote: > Vadym Chepkov wrote: > > A company I work for is trying to migrate their applications to > > Linux platform and have selected RedHat as the vendor. Redhat > > installs bash as the standard shell : > > > $ ls -l /bin/sh > > lrwxrwxrwx 1 root root 4 Jul 7 2009 /bin/sh -> bas

Re: patch bash32-049 is missing from bash 4.0

> It seems that patch > > http://ftp.gnu.org/gnu/bash/bash-3.2-patches/bash32-049 > > was left from version 4.0. > > Anyone has comment on this? Can this be radded? The changed code is in bash-4.1. Why not just move to that? I put out a patch for 3.2 to accommodate Sun and other vendors, but

patch bash32-049 is missing from bash 4.0

Hi, It seems that patch http://ftp.gnu.org/gnu/bash/bash-3.2-patches/bash32-049 was left from version 4.0. Anyone has comment on this? Can this be radded? Thanks, Petr

Re: bash exit command should be unconditional

On Thu, Apr 08, 2010 at 06:05:05AM -0700, Vadym Chepkov wrote: > A company I work for is trying to migrate their applications to Linux > platform and have selected RedHat as the vendor. Redhat installs bash as the > standard shell : > $ ls -l /bin/sh > lrwxrwxrwx 1 root root 4 Jul 7 2009 /bin/sh

Re: bash exit command should be unconditional

On 04/08/2010 07:11 AM, Matias A. Fonzo wrote: > If I am right when you invoke bash as "/bin/sh" (/bin/sh -> bash). Bash > runs in POSIX mode. Correct. But POSIX allows shells to decide whether or not commands in pipelines operate in the current shell or a subshell. > >> I certainly have chosen

Re: bash exit command should be unconditional

If I am right when you invoke bash as "/bin/sh" (/bin/sh -> bash). Bash runs in POSIX mode. > I certainly have chosen the subject wrong, but I don't want to start a new > thread now. Please let me backpedal a bit and describe the problem I am > trying to solve. > > A company I work for is trying t

Re: bash exit command should be unconditional

I certainly have chosen the subject wrong, but I don't want to start a new thread now. Please let me backpedal a bit and describe the problem I am trying to solve. A company I work for is trying to migrate their applications to Linux platform and have selected RedHat as the vendor. Redhat insta

Re: bash exit command should be unconditional

On 04/08/2010 06:49 AM, Bob Proulx wrote: Vadym Chepkov wrote: I found out a very unusual feature of bash which makes it to act really unexpected. I understand that pipelines are executed in a separate subshell, but I really think 'exit' command should be absolute. Consider a trivial code: