Re: Question about monitor mode / ignoreeof / EOF read

Chet Ramey wrote in : |On 1/16/23 6:35 PM, Steffen Nurpmeso wrote: |> It turns out that the inner shell tries to set the process group |> (to the parent shell which no longer exists), then causing the |> interactive bash on the terminal to read an EOF next, and without |> ignoreeof set the

Re: Question about monitor mode / ignoreeof / EOF read

On 1/16/23 6:35 PM, Steffen Nurpmeso wrote: It turns out that the inner shell tries to set the process group (to the parent shell which no longer exists), then causing the interactive bash on the terminal to read an EOF next, and without ignoreeof set the interactive shell then exits. (This

Re: Question about case statement in Bash docs

On 5/10/21 10:40 AM, Andreas Schwab wrote: On Mai 10 2021, Chet Ramey wrote: Either way, quote removal happens, the double quotes are removed, and the characters between the double quotes are treated specially. POSIX doesn't mention quote removal either. Is that a bug? There is the

Re: Question about case statement in Bash docs

On Mai 10 2021, Chet Ramey wrote: > Either way, quote removal happens, the double quotes are removed, and > the characters between the double quotes are treated specially. POSIX doesn't mention quote removal either. Is that a bug? There is the parenthetical remark "(which also describes the

Re: Question about case statement in Bash docs

On 5/10/21 10:23 AM, Andreas Schwab wrote: On Mai 10 2021, Greg Wooledge wrote: On Mon, May 10, 2021 at 09:12:33PM +1000, AlvinSeville7cf wrote: x=test case $x in "test") echo Y esac Pattern is quoted but no quote removal is performed according to docs. Quote

Re: Question about case statement in Bash docs

On Mai 10 2021, Greg Wooledge wrote: > On Mon, May 10, 2021 at 09:12:33PM +1000, AlvinSeville7cf wrote: >>x=test >>case $x in >>"test") echo Y >>esac >> >>Pattern is quoted but no quote removal is performed according to docs. > > Quote removal is essential, because of the

Re: Question about case statement in Bash docs

On 5/10/21 7:12 AM, AlvinSeville7cf wrote: Hello! Let’s consider the following snippet from [1]Bash docs: case word in [ [(] pattern [| pattern]…) command-list ;;]… esac It is written that: Each pattern undergoes tilde expansion, parameter expansion, command substitution, and

Re: Question about case statement in Bash docs

On Mon, May 10, 2021 at 09:12:33PM +1000, AlvinSeville7cf wrote: >x=test >case $x in >"test") echo Y >esac > >Pattern is quoted but no quote removal is performed according to docs. Quote removal is essential, because of the way the empty string is matched: case $foo in

Re: Question about help information for the printf command

On 9/9/19 10:45 PM, 2477441814 wrote: > Dear team, > > > when I invoke 'help printf' in terminal to view help manual, It shown me '%b > %q %(fmt)T' is an addition to printf(1) and printf(3), The online version of > bash manual from (http://www.gnu.org/software/bash/manual/bash.html) does >

Re: question on retrieving map(-A) value w/indirect name

On Fri, Mar 16, 2018 at 05:50:04PM -0700, L A Walsh wrote: > If I have assoc-array: > > declare -A foo=([one]=11 [two]=22) > > and am passing name in another var, like "fee" > > fee=foo > > I tried echoing the val: > > echo ${!fee[one]} > > but got nothing -- tried a few other syntaxes.

Re: question on retrieving map(-A) value w/indirect name

David Margerison wrote: processSrvState() { local cur_up="$1[cur_up]" local max_up="$1[max_up]" if [[ "${!cur_up}" == "${!max_up}" ]] ; then echo ok fi } declare -A foo=([cur_up]=11 [max_up]=11) processSrvState foo # note that the array name must not conflict with any keys

Re: question on retrieving map(-A) value w/indirect name

On 17 March 2018 at 20:40, L A Walsh wrote: > > I seebut that begs the question, how do you access an array's > members using a var holding the array's name? > > I wanted to be able to do something like have a set of > values in an assoc. map, and pass the name to a generic >

Re: question on retrieving map(-A) value w/indirect name

On 17 March 2018 at 11:50, L A Walsh wrote: > > I'm a bit confused ... > If I have assoc-array: > > declare -A foo=([one]=11 [two]=22) > > and am passing name in another var, like "fee" > > fee=foo > > I tried echoing the val: > > echo ${!fee[one]} > > but got nothing -- tried

Re: question on retrieving map(-A) value w/indirect name

Chet Ramey wrote: On 3/16/18 8:50 PM, L A Walsh wrote: I'm a bit confused ... If I have assoc-array: declare -A foo=([one]=11 [two]=22) and am passing name in another var, like "fee" fee=foo I tried echoing the val: echo ${!fee[one]} but got nothing -- tried a few other syntaxes.

Re: question on retrieving map(-A) value w/indirect name

On 3/16/18 8:50 PM, L A Walsh wrote: > > I'm a bit confused ... > If I have assoc-array: > >  declare -A foo=([one]=11 [two]=22) > > and am passing name in another var, like "fee" > >  fee=foo > > I tried echoing the val: > >  echo ${!fee[one]} > > but got nothing -- tried a few other

Re: (OffTopic,) Gnu-Environment restrictions (was Re: Question )

Robert Elz wrote: > I will send one more reply on this topic - I am replying to this message > as I agree with the change of Subject - this is off topic for this list, > which is why I will not respond any further to messages about this here. You are most enlightened and I will do the same with

Re: (OffTopic,) Gnu-Environment restrictions (was Re: Question )

I will send one more reply on this topic - I am replying to this message as I agree with the change of Subject - this is off topic for this list, which is why I will not respond any further to messages about this here. Bob Proulx said (in a message with the original subject):

(OffTopic,) Gnu-Environment restrictions (was Re: Question )

Bob Proulx wrote: Robert Elz wrote: But any restrictions on the recipient mean that the software is not really free, and that includes nonsense like requiring users to redistribute the sources to anyone who wants it. That's not freedom, that's an obligation (serfdom - you have to do my work

Re: Question

Robert Elz wrote: > Bob Proulx wrote: > > However this difference in philosophy does not change the technology > > that creating a compiler for an interpreted language is very hard. > > Maybe impossible. > > No. Not impossible, not even all that difficult, just in this case, > not all that

Re: Question

On 9/16/17 11:16 PM, Robert Elz wrote: > Now to the philosophical ... I agree with the aims of free software, but > I believe that should be interpreted correctly - that is, if software is > free, it should impose no restrictions at all upon is recipients, which > includes hidden "you should

Re: Question

Date:Thu, 14 Sep 2017 20:22:04 -0600 From:Bob Proulx Message-ID: <20170914195843892632...@bob.proulx.com> | However this difference in philosophy does not change the technology | that creating a compiler for an interpreted language is very hard.

Re: Question

Saint Michael wrote: > I use Linux. My business to provide services for problems that I solve, as > you mention, by calling Awk, sed, join, etc., and databases. Sounds good. I classify myself the same way. :-) > I allow my customers to login to a box that I provide in my > datacenter. I cannot

Re: Question

Dear Bob I use Linux. My business to provide services for problems that I solve, as you mention, by calling Awk, sed, join, etc., and databases. I allow my customers to login to a box that I provide in my datacenter. I cannot accept that it is impossible to restrict them to only call my *,sh

Re: Question

Saint Michael wrote: > Dear Maintainer Note that I am not the maintainer. > Is there a commercial or free software that can take a Bash script and > transparently turn it into a C executable, provided the machines where it > runs has any of the external commands like awk, etc? Not as far as I

Re: Question about arithmetic expression grammar

2016-10-08 17:33:00 +0200, Conrad Hoffmann: [...] > $ TEST=5; echo $((--TEST+++3)) # outputs 7 > > However, due to the documented operator precedence, I would have > expected that expression to be equal to: > > $ TEST=5; echo $((--(TEST++)+3)) # outputs 8 > > Instead, though, it seems to be

Re: Question: is this a bug in BASh (pre-exec trap)

On 9/9/16 2:00 PM, Matthew Giassa wrote: > Good day, > > I've been doing some testing with the bash-prexec script which uses a > DEBUG trap to issue user-supplied functions before executing each > command (https://github.com/rcaloras/bash-preexec). > > Here is a minimal working example >

Re: question of command cd's option [-e]

On 1/14/13 9:20 PM, MaShimiao wrote: Bash Version: 4.2 Patch Level: 28 Release Status: release Description: I want to use the option [-e] of command cd. But I found I can't use. Thanks for the report, good catch. This will be fixed in the next release. Chet -- ``The lyf so short,

Re: question of command cd's option [-e]

I'd also suggest to simplify the synopsis. cd [-LPe] [dir] Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 And now for something completely different.

Re: question of command cd's option [-e]

On Tue, Jan 15, 2013 at 9:19 AM, Andreas Schwab sch...@linux-m68k.orgwrote: I'd also suggest to simplify the synopsis. cd [-LPe] [dir] Andreas. -e is only used with -P, so the current synopsis makes more sense and is clearer, IMO. DJ

Re: question of command cd's option [-e]

DJ Mills danielmil...@gmail.com writes: -e is only used with -P, so the current synopsis makes more sense and is clearer, IMO. You can use -e also with -L, it just doesn't have an effect. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3

Re: Question on periods in function names

On 1/5/13 9:11 AM, muji wrote: Hello! According to this: http://tldp.org/LDP/abs/html/gotchas.html As of version 3 periods in function names are not allowed, I quote: # As of version 3 of Bash, periods are not allowed within function names. Yet I am using: GNU bash, version

Re: Question about the return value of 'local'

On Fri, Dec 14, 2012 at 08:37:02AM +0100, Francis Moreau wrote: Then maybe an option should be added to 'local' to display the full description that one can get from the manual, or maybe change the behaviour of '-m' switch ? Almost every builtin command has a shorter and less informative

Re: Question about the return value of 'local'

On Fri, Dec 14, 2012 at 2:21 PM, Greg Wooledge wool...@eeg.ccf.org wrote: On Fri, Dec 14, 2012 at 08:37:02AM +0100, Francis Moreau wrote: Then maybe an option should be added to 'local' to display the full description that one can get from the manual, or maybe change the behaviour of '-m'

Re: Question about the return value of 'local'

On 12/14/12 2:37 AM, Francis Moreau wrote: `help' is a quick reference -- a handy shortcut. The authoritative documentation is still the manual page and texinfo document. Then maybe an option should be added to 'local' to display the full description that one can get from the manual, or

Re: Question about the return value of 'local'

On 12/14/12 8:21 AM, Greg Wooledge wrote: I do sympathize with the difficulty of finding the relevant information in the manual sometimes, though, especially for builtins that are common words like 'set'. That's where the superior indexing and structure of the info file format demonstrate

Re: Question about the return value of 'local'

On Friday, December 14, 2012 08:37:02 AM Francis Moreau wrote: On Thu, Dec 13, 2012 at 3:19 PM, Chet Ramey chet.ra...@case.edu wrote: On 12/13/12 3:56 AM, Francis Moreau wrote: I see thanks. Somehow I thought that help(1) would have given nothing more nothing less than what was

Re: Question about the return value of 'local'

I'm not trying to start a war, but ... Has anyone entertained the idea of getting rid of the man pages and the info system? Those are relics of the tty era. We have graphical interfaces today with capabilities that could enhance providing and then finding better information. Wouldn't a browser

Re: Question about the return value of 'local'

On 12/14/2012 12:07 PM, Bill Gradwohl wrote: I'm not trying to start a war, but ... Has anyone entertained the idea of getting rid of the man pages and the info system? Those are relics of the tty era. We have graphical interfaces today with capabilities that could enhance providing and then

Re: Question about the return value of 'local'

On 12/14/2012 06:07 PM, Bill Gradwohl wrote: I'm not trying to start a war, but ... Has anyone entertained the idea of getting rid of the man pages and the info system? Those are relics of the tty era. Don't make the error of confusing the texinfo system with just the info format. I, for

Re: Question about the return value of 'local'

On 12/14/2012 06:58 PM, Bill Gradwohl wrote: My point was to DESIGN for html and the rich environment it offers, not to try to convert a Model T into a Mercedes. I'm not wild about a wiki either, if its a free for all. If on the other hand, it is a submission platform that gets reviewed and

Re: Question about the return value of 'local'

Francis Moreau wrote: I found that the return value of 'local' keyword is counter intuitive when the value of the assignment is an expression returning false. In that case the return value of local is still true. For example: local foo=$(echo bar; false) returns true Yes. The creation

Re: Question about the return value of 'local'

Francis Moreau francis.m...@gmail.com writes: The help of 'local' is rather obscure about the description on its return value: Returns success unless an invalid option is supplied, an error occurs, or the shell is not executing a function. an error occurs is rather meaningless

Re: Question about the return value of 'local'

On Thu, Dec 13, 2012 at 9:44 AM, Bob Proulx b...@proulx.com wrote: Francis Moreau wrote: I found that the return value of 'local' keyword is counter intuitive when the value of the assignment is an expression returning false. In that case the return value of local is still true. For example:

Re: Question about the return value of 'local'

On Thu, Dec 13, 2012 at 9:44 AM, Andreas Schwab sch...@linux-m68k.org wrote: Francis Moreau francis.m...@gmail.com writes: The help of 'local' is rather obscure about the description on its return value: Returns success unless an invalid option is supplied, an error occurs, or the

Re: Question about the return value of 'local'

On 12/13/12 3:56 AM, Francis Moreau wrote: I see thanks. Somehow I thought that help(1) would have given nothing more nothing less than what was described in the manual. `help' is a quick reference -- a handy shortcut. The authoritative documentation is still the manual page and texinfo

Re: Question about the return value of 'local'

Actually I was asking for the case when 'local' is not used: foo=$(echo bar; false) this assignment expression returns false, and I'm wondering where that's documented. Look in the SIMPLE COMMAND EXPANSION section of the man page: If there is a command name left after

Re: Question about the return value of 'local'

On Thu, Dec 13, 2012 at 3:25 PM, Chet Ramey chet.ra...@case.edu wrote: Actually I was asking for the case when 'local' is not used: foo=$(echo bar; false) this assignment expression returns false, and I'm wondering where that's documented. Look in the SIMPLE COMMAND EXPANSION section of

Re: Question about the return value of 'local'

On Thu, Dec 13, 2012 at 3:19 PM, Chet Ramey chet.ra...@case.edu wrote: On 12/13/12 3:56 AM, Francis Moreau wrote: I see thanks. Somehow I thought that help(1) would have given nothing more nothing less than what was described in the manual. `help' is a quick reference -- a handy shortcut.

Re: Question about patterns

On 06/23/2011 03:59 PM, Steven W. Orr wrote: I may be wrong, but I think there's a way to do what I want without using a regex. I have a file called foo-1.2-3.tar.gz I need to set a variable equal to foo-1.2-i386-x86_64-3.tar.gz Is there a way to do this without parsing my brains out? I am

Re: Question about patterns

On 06/23/2011 04:56 PM, Roman Rakus wrote: On 06/23/2011 03:59 PM, Steven W. Orr wrote: I may be wrong, but I think there's a way to do what I want without using a regex. I have a file called foo-1.2-3.tar.gz I need to set a variable equal to foo-1.2-i386-x86_64-3.tar.gz Is there a way to do

Re: Question about patterns

On 6/23/11 9:59 AM, Steven W. Orr wrote: I may be wrong, but I think there's a way to do what I want without using a regex. I have a file called foo-1.2-3.tar.gz I need to set a variable equal to foo-1.2-i386-x86_64-3.tar.gz Is there a way to do this without parsing my brains out? I am

Re: Question about testing with variable operators

On 6/10/11 11:44 AM, Steven W. Orr wrote: As a work around, I can use eval or the builtin test, but my question is this: Is this a bug or is there a reason that it should work for arithmetic but not for the test [[ operator? It's not a bug. The (( command is syntactic sugar: (( ...)) is

Re: Question about testing with variable operators

Andreas Schwab wrote: Steven W. Orr ste...@syslang.net writes: As a work around, I can use eval or the builtin test, but my question is this: Is this a bug or is there a reason that it should work for arithmetic but not for the test [[ operator? [[ is a reserved word like if, which triggers

Re: Question about testing with variable operators

Steven W. Orr ste...@syslang.net writes: As a work around, I can use eval or the builtin test, but my question is this: Is this a bug or is there a reason that it should work for arithmetic but not for the test [[ operator? [[ is a reserved word like if, which triggers special parsing rules,

Re: Question about arithmetic logic.

On Mon, Apr 18, 2011 at 10:30:35AM -0400, Steven W. Orr wrote: ss=1 (( ss )) echo $? # Also says 1. Should this be 0 because it should be the # success result same as (( ss != 0 )) That's not what I get: imadev:~$ unset ss; ss=0; ((ss)); echo $? 1 imadev:~$

Re: Question about arithmetic logic.

On 04/18/2011 04:30 PM, Steven W. Orr wrote: I happen to be running GNU bash, version 4.0.35(1)-release (x86_64-redhat-linux-gnu) I create an integer variable and assign it either a 0 or a 1. The arithmetic test always returns success regardless of value. For example: typeset -i ss=0 (( ss

Re: Question about arithmetic logic.

On 4/18/11 10:30 AM, Steven W. Orr wrote: I happen to be running GNU bash, version 4.0.35(1)-release (x86_64-redhat-linux-gnu) I create an integer variable and assign it either a 0 or a 1. The arithmetic test always returns success regardless of value. For example: $ cat x20 unset ss;

Re: Question about arithmetic logic.

On 4/18/2011 10:40 AM, Greg Wooledge wrote: On Mon, Apr 18, 2011 at 10:30:35AM -0400, Steven W. Orr wrote: ss=1 (( ss )) echo $?# Also says 1. Should this be 0 because it should be the # success result same as (( ss != 0 )) That's not what I get:

Re: Question about arithmetic logic.

On Mon, Apr 18, 2011 at 10:57:00AM -0400, Steven W. Orr wrote: I get the same result as you when I do it your way. But if I add the typeset, I still get the same result: 515 unset ss; typeset -i ss=1; ((ss)); echo $? 0 516 unset ss; typeset -i ss=0; ((ss)); echo $? 1 Interesting. So

Re: Question about arithmetic logic.

Sorry to bother. I have no idea why it works now and did not before. Obvious case of cockpit error. :-( On 4/18/2011 10:30 AM, Steven W. Orr wrote: I happen to be running GNU bash, version 4.0.35(1)-release (x86_64-redhat-linux-gnu) I create an integer variable and assign it either a 0 or a

Re: Question. Autocomplete paths starting with %.

On Sat, Feb 19, 2011 at 9:20 PM, d...@ucore.info d...@ucore.info wrote: I can script in Bash quite well, but I've never did anything that fancy with completion and I don't know how to plug my function to handle this. I understand that I should register something (function named like

Re: question about exit command

On Wednesday 19 Jan 2011 10:42:21 ali hagigat wrote: I have two script files and I execute them as follows: - #script1 echo ppp exit 0 echo qqq /root ./script1 ppp - #script2 if (exit 0) then echo ppp fi

Re: question about exit command

On Wed, Jan 19, 2011 at 10:49:47AM +, Davide Brini wrote: In your second script, the exit 0 part runs in a subshell, so exit exits that subshell (and I'm somewhat surprised that no semicolon is required after the closing bracket, but I may have missed something in the grammar). He had

Re: question about exit command

On Wed, Jan 19, 2011 at 01:43:34PM +, Davide Brini wrote: From wikipedia: Parentheses (singular, parenthesis) ??? also called simply brackets (UK), or round brackets, curved brackets, oval brackets, or, colloquially, parens... Oh joy... another weird British thing I wasn't aware of.

Re: Question regarding pathname expansion

Oops - never mind. I see my error. ls /usr* will list all files within usr usr2 directories. the / is needed to specify the files within. Thank you! javajo91 wrote: Morning - I'm reading Learning the bash Shell by Newham Rosenblatt and have a question regarding pathname expansion

Re: Question if bug: declaration of an associative array within a function

On Tue, 15 Jun 2010, Rainer Rehak wrote: Hey there, is it a bug, that the declaration of an associative array within a function does not survive till after the function, with primitive variables on the other hand that concept works well. It's not a bug. It's an unfortunate side effect

Re: Question if bug: declaration of an associative array within a function

On Tue, Jun 15, 2010 at 01:21:51PM +0200, Rainer Rehak wrote: Hey there, is it a bug, that the declaration of an associative array within a function does not survive till after the function, with primitive variables on the other hand that concept works well. `declare' has the side effect of

Re: Question if bug: declaration of an associative array within a function

On 6/15/10 5:22 PM, Greg Wooledge wrote: `declare' has the side effect of making things local to a function, if it is used within a function. There is currently no way to create a global associative array while inside a function; you'd have to do it outside the function. Chet has said, I

Re: Question (and maybe, a suggestion)

Pablo Rodríguez Fernández wrote: Why there are some keyboard shortcuts that don't appear on man and web page manual? I've found some shortcuts very useful (and widely knowed by bash users) on this blog: http://linuxhelp.blogspot.com/2005/08/bash-shell-shortcuts.html and most of them are on

Re: Question

On Thu, 2 Apr 2009 18:33:40 -0700, Brandon F wrote: When I do traceroute in bash I am always getting 12-215-11-193.client.mchsi.com as the third or fourth site. I want to know how to clear this from my route list. So it will bounce off of a differant site. Thank you. What a _clever_ Subject:

Re: Question

On Thursday 02 April 2009 21:33:40 Brandon F wrote: When I do traceroute in bash traceroute is not part of bash I am always getting 12-215-11-193.client.mchsi.com as the third or fourth site. I want to know how to clear this from my route list. So it will bounce off of a differant site.

Re: Question

Brandon F wrote: When I do traceroute in bash I am always getting 12-215-11-193.client.mchsi.com as the third or fourth site. I want to know how to clear this from my route list. So it will bounce off of a differant site. Thank you. Bash is running the program traceroute for you. Having

Re: Question

On Friday 3 April 2009 03:33, Brandon F wrote: When I do traceroute in bash I am always getting 12-215-11-193.client.mchsi.com as the third or fourth site. I want to know how to clear this from my route list. So it will bounce off of a differant site. Thank you. traceroute | sed

Re: Question about behavior of redirections inside an if construct

Thomas Schwinge tschwi...@gnu.org writes: These three work as expected. But why doesn't the following one? tho...@dirichlet:~ $ sh -c 'if : 2 /dev/null NONEXISTING_FILE; then :; else echo 2 OK; fi' Works fine here. Are you sure sh is Bash? Andreas. -- Andreas Schwab, SuSE Labs,

Re: Question on bash clearwildcards

grendelos wrote: So this is really bugging me. Why is [a-z] not case sensitive, but [A-Z] is? For example: # ls -l total 0 -rw-r--r-- 1 root root 0 Nov 20 12:22 xa -rw-r--r-- 1 root root 0 Nov 20 12:22 xA # ls -l x[a-z] -rw-r--r-- 1 root root 0 Nov 20 12:22 xa -rw-r--r-- 1 root root

Re: Question about inline code / incompatibility between FreeBSD sh and bash

On Thu, Jun 19, 2008 at 2:12 AM, Garrett Cooper [EMAIL PROTECTED] wrote: Hi, Sorry for emailing this list, but neither the GNU indexed homepage nor the actual project page listed any other email address. I'm trying to determine whether or not this is an implicit bug or a feature of

Re: Question about inline code / incompatibility between FreeBSD sh and bash

On Thu, Jun 19, 2008 at 2:29 AM, Garrett Cooper [EMAIL PROTECTED] wrote: On Thu, Jun 19, 2008 at 2:12 AM, Garrett Cooper [EMAIL PROTECTED] wrote: /usr/sbin/portsnap: portsnap: line 882: syntax error near unexpected token `newline' /usr/sbin/portsnap: portsnap: line 882: ` if !'

Re: Question about inline code / incompatibility between FreeBSD sh and bash

Garrett Cooper [EMAIL PROTECTED] writes: Hi, Sorry for emailing this list, but neither the GNU indexed homepage nor the actual project page listed any other email address. I'm trying to determine whether or not this is an implicit bug or a feature of BSD bourne shell (in particular

Re: question and/or enhancement request

On 7/29/07, Erick Wodarz [EMAIL PROTECTED] wrote: I think the following is hard (or impossible?) using bash. I want to create a shell script that will ... This may be possible, depending on exactly what you need, but you'd probably be better off trying `expect'. #!/bin/bash mknod

Re: Question about variables and for loop

Bob [EMAIL PROTECTED] wrote: XXX='a b c d' for x in $XXX ; do echo $x done XXX='a b c d' eval set $XXX for x in $@ ; do echo $x done If the first element in XXX might start with -, then it takes a little more work to ensure it isn't misinterpreted as

Re: Re: Question

Auto-response to Re: Question Thank you for your email! It will be read and answered within the next two or three days. In order to keep this service free, we need to streamline the support process. Your help is deeply appreciated. To that goal, we request that ALL SUPPORT REQUESTS CONTAIN

Re: Question

Norman Virus Control a supprim le message original qui contenait le virus [EMAIL PROTECTED] ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash