Possible Feature Requests (unsource, exchange)

2009-07-07 Thread Christopher Roy Bratusek
Hi all, what I'm currently missing are the following two things (I'm not 100% sure if they are not available): unsource: the opposite of source (while source is making functions publically available, unsource would remove them) exchange: exchanges the value of two variables (x=2 y=a; exchange x

Re: Possible Feature Requests (unsource, exchange)

2009-07-07 Thread Greg Wooledge
On Tue, Jul 07, 2009 at 08:16:50PM +0200, Christopher Roy Bratusek wrote: > unsource: the opposite of source (while source is making functions > publically available, unsource would remove them) You can "unset -f" a function. You could source a script-file that contains a bunch of "unset -f foo"

Re: Possible Feature Requests (unsource, exchange)

2009-07-07 Thread Dave B
On Tuesday 07 July 2009, Christopher Roy Bratusek wrote: > Hi all, > > what I'm currently missing are the following two things (I'm not 100% > sure if they are not available): > > unsource: the opposite of source (while source is making functions > publically available, unsource would remove them)

Re: Need info on input keys

2009-07-07 Thread Anuz Pratap Singh Tomar
No top posting, please. On Tue, Jul 7, 2009 at 5:15 PM, seshikanth varma wrote: > Just a Gentle reminder. Any of ur thoughts would be really helpful, > > > > > On Tue, Jul 7, 2009 at 12:17 PM, seshikanth varma < > seshikanthva...@gmail.com> wrote: > >> Adding bug-bash@gnu.org in loop >> >> Thanks

Re: Need info on input keys

2009-07-07 Thread seshikanth varma
Adding bug-bash@gnu.org in loop Thanks, On Tue, Jul 7, 2009 at 12:11 PM, SandeepKsinha wrote: > Hi Shashikanth, > > > On Mon, Jul 6, 2009 at 10:54 PM, seshikanth > varma wrote: > > Hi All, > > > > I need to implement history feature in an emulated shell environment. I > need > > to read keys pre

Re: Need info on input keys

2009-07-07 Thread seshikanth varma
Just a Gentle reminder. Any of ur thoughts would be really helpful, On Tue, Jul 7, 2009 at 12:17 PM, seshikanth varma wrote: > Adding bug-bash@gnu.org in loop > > Thanks, > > > On Tue, Jul 7, 2009 at 12:11 PM, SandeepKsinha wrote: > >> Hi Shashikanth, >> >> >> On Mon, Jul 6, 2009 at 10:54 PM,

Problem with a "for"

2009-07-07 Thread tirengarfio
Hi, im trying to write a script to check the port 22 of 4 IPs. IPS={89.17.206.180,89.17.206.185,89.17.206.186,89.17.206.187} for i in ${IPS} do nmap -p 22 {IPS} done but i get this error: Failed to resolve given hostname/IP: {IPS}. Note that you can't use '/mask' AND '1-4,7,100-' style IP r

Re: Problem with a "for"

2009-07-07 Thread Bob Proulx
tirengarfio wrote: > IPS={89.17.206.180,89.17.206.185,89.17.206.186,89.17.206.187} Check the value that you assigned using echo. $ echo "$IPS" {89.17.206.180,89.17.206.185,89.17.206.186,89.17.206.187} Notice that brace expansion hasn't occurred in variable assignment. In the bash manual it

Re: Problem with a "for"

2009-07-07 Thread Jon Seymour
There are at least 3 things wrong with your snippet. Try: IPS=(( 89.17.206.180 89.17.206.185 89.17.206.186 89.17.206.187 )) for k in ${i...@]} do nmap -p 22 $k done jon. On 07/07/2009, at 4:55 AM, tirengarfio wrote: IPS={89.17.206.180,89.17.206.185,89.17.206.186,89.17.206.187}