Right behavior of -x option?

In RH bugzilla we have open bug impeaching right behavior of -x option. Reporter is using japanese environment and is trying: bash -x -c "echo \"あいうえお\"" echoing any japanese sentence. and bash write out: + echo $'\343\201\202\343\201\204\343\201\206\343\201\210\343\201\212' sentence in octal d

Re: Right behavior of -x option?

> In RH bugzilla we have open bug impeaching right behavior of -x option. > Reporter is using japanese environment and is trying: > > bash -x -c "echo \"あいうえお\"" > > echoing any japanese sentence. > > and bash write out: > + echo $'\343\201\202\343\201\204\343\201\206\343\201\210\343\2

Add a new internal command to BASH

Hi i wanted to add a new internal command to bash, how shall i do it. please help me out on this, trying to do this since many days. i'm not looking for any alias etc stuffs, i want to my own command as bash built in commands like trap, eval etc Thanks Abhinandan -- View this message in context:

Re: Add a new internal command to BASH

Have you tried simply creating the executable (or script) and placing it in your PATH somewhere? Regards, Michael On May 22, 2008, at 5:17 AM, Abhinandan wrote: Hi i wanted to add a new internal command to bash, how shall i do it. please help me out on this, trying to do this since many d

Bash for OS/2

Hello. With some effort and help, I have Bash 3.1 built and mostly working under OS/2. This uses gcc 3.3.5 with "kLIBC" 0.6.3, rather than the old EMX tools. 3.2 needs a bit more work, and some of the patches might need some more polish. My questions: Are you interested in these patches? If so,

Re: Bash for OS/2

On Thursday 22 May 2008, Brendan Oakley wrote: > With some effort and help, I have Bash 3.1 built and mostly working > under OS/2. This uses gcc 3.3.5 with "kLIBC" 0.6.3, rather than the > old EMX tools. 3.2 needs a bit more work, and some of the patches > might need some more polish. My questions:

Re: Add a new internal command to BASH

Hi, thats not what i intend to do. I want to write my own command and compile the bash source and then run that command as bash built in command [EMAIL PROTECTED] wrote: > > Have you tried simply creating the executable (or script) and placing > it in your PATH somewhere? > > Regards, > Mic

Re: Add a new internal command to BASH

Abhinandan wrote: > [EMAIL PROTECTED] wrote: > > Abhinandan wrote: > > > I wanted to add a new internal command to bash, how shall I do it. > > > > Have you tried simply creating the executable (or script) and placing > > it in your PATH somewhere? > > thats not what i intend to do. I want to wri

Re: Add a new internal command to BASH

On Thursday 22 May 2008, Bob Proulx wrote: > If you still want to modify the source that is okay. You are free to > do so. Grab the source and modify it as you desire. But in order to > get help from other people you would need to motivate them as to why > you are one of the 0.01% of the peo

Re: Bash for OS/2

On Thu, May 22, 2008 at 8:04 PM, Mike Frysinger <[EMAIL PROTECTED]> wrote: > On Thursday 22 May 2008, Brendan Oakley wrote: >> With some effort and help, I have Bash 3.1 built and mostly working >> under OS/2. This uses gcc 3.3.5 with "kLIBC" 0.6.3, rather than the >> old EMX tools. 3.2 needs a bit

Re: Bash for OS/2

On Friday 23 May 2008, Brendan Oakley wrote: > I would like to see them included, so the crucial part of my question > is whether it would be proper to submit any incremental patches for > inclusion even while the port itself is, in some ways, incomplete; or > whether I should have everything right