Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Frank Winkler <usenet@f.winkler-ka.de>
Newsgroups: comp.unix.shell
Subject: Re: Variable var names
Date: Fri, 12 Jun 2026 14:07:41 +0200
Lines: 10
Message-ID: <n92b4dFmk8aU1@mid.individual.net>
References: <n91qs8Fk65fU1@mid.individual.net> <spaces-20260612122522@ram.dialup.fu-berlin.de> <dots-20260612123818@ram.dialup.fu-berlin.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net VA22njFnhVnbwa847Yr2Ggl5UNoC2fKnhW/hKysB0uPjILGlO9
Cancel-Lock: sha1:LsdwymzLwnTpWLrX/G1E2Bnbn80= sha256:/u4r3NMnbfD4KP+y7WvCfU1op4tbx/uvZyci2WZOwqM=
User-Agent: Mozilla Thunderbird Beta
Content-Language: en-US
In-Reply-To: <dots-20260612123818@ram.dialup.fu-berlin.de>
Xref: csiph.com comp.unix.shell:26907

On 12.06.2026 13:38, Stefan Ram wrote:

  >> |x with leading and trailing spaces stripped. The shell, not echo!

Sure - and that's why I also quoted the variable, which should keep the 
blanks - shouldn't it?

  >   . So, the behavior of IFS probably is due to the dots "." used.
No, it's not. I just added the dots here to clarify that the blanks get 
lost.