Re: Help me upgrading Bash

On Thu, 8 Feb 2007, San wrote: > Dear Sir, > You will need to tell people, generally in cases like this, what your platform is. > I have tried installing the latest version of BASH (3.2) but whenever i > start the terminal, & type "bash --version" but still i get v2.05. Please > tell me in d

Re: Just created alias doesn't work in a string of commands

"Gurjeet Singh" <[EMAIL PROTECTED]> wrote: > 1$ cat setenv.sh > #!/bin/sh > > alias llrt='ls -lrt' ... > 5$ . ./setenv.sh && llrt && . ./unsetenv.sh > sh: llrt: command not found Aliases are expanded when a command is read, not when it is executed. The entire && chain of commands forms a single co

Help me upgrading Bash

Dear Sir, I have tried installing the latest version of BASH (3.2) but whenever i start the terminal, & type "bash --version" but still i get v2.05. Please tell me in detail the steps needed to have the latest version on the system. Thanks & Regards, San. -

How to upgrade the BASH ?

Dear Sir, I am having Bash version 2.05 on my system. I want to upgrade it to version 3.2 Please help me how to do this. I sincerely hope that you will help me in this regard & oblige. Thanks. San. - Everyone is raving about the all-new Yahoo! Mai

Re: bash 3.2, escape sequences

> Sebastian Kapfer wrote: > >> I'm not quite getting the changes in bash's handling of escape >> sequences. > > I can't reproduce your results: [...] > I suspect that you have echo defined as a function or alias, or > something in $PROMPT_COMMAND or $PS1 is obscuring the output. Oops, I thought

Just created alias doesn't work in a string of commands

I am using MinGW, and found this bug. Following is the session that shows a reproducible test-case. The steps are elaborated here (numbers before the dollar prompt) 0) Shows the version information. 1) Shows that setenv.sh sets an alias (llrt) 2) Shows that unsetenv.sh unsets the alias (llrt) 3)

Re: help on bash-3.2

I compiled bash-3.2.0 from source (bash-3.2.tar.gz). After installation i get errors at configuring different software, especially at my KDE-project. I tried also different types of bash (features - more or less) - always this error. When I downloaded bash I haven't seen a patch to this version,

Re: readline: edit (mode:vi) means eol unreachable

On Thu, 8 Feb 2007, Chet Ramey wrote: > Hugh Sasse wrote: > > >> either they need to be in termcap/terminfo or you need to bind them > >> yourself in .inputrc. If the key sequence isn't bound, it will be > > > > Either strategy is equally valid? Well, I'm trying to get terminfo > > right. >

Re: readline: edit (mode:vi) means eol unreachable

Hugh Sasse wrote: >> either they need to be in termcap/terminfo or you need to bind them >> yourself in .inputrc. If the key sequence isn't bound, it will be > > Either strategy is equally valid? Well, I'm trying to get terminfo > right. Sure, either way is OK from readline's perspective --

Re: readline: edit (mode:vi) means eol unreachable

On Wed, 7 Feb 2007, Chet Ramey wrote: > Hugh Sasse wrote: > > >> I'm not sure I understand the question. If the termcap/terminfo entries > > > > The question is about the vi edit mode for a correctly configured > > terminal, with no personalization. Should the cursor keys take me > > out of in