hi there,

I bumped into a weird machine in my office where in the command window when
I type in
FOR /F "usebackq delims==" %i IN (`set`) DO @echo %i

and hit enter, the command window will just close down completely like I
just issue the EXIT command.

This only happen to
FOR /F ["options"] %variable IN (`command`) DO command
[command-parameters]

If i just use the FOR to parse the content of a file, then everthing just
work as expected.

Anyone seen this kind of problem before?

Forgot to mention the Os is WinXp SP2

"Kok Yong Lee" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> hi there,
>
> I bumped into a weird machine in my office where in the command window
> when I type in
> FOR /F "usebackq delims==" %i IN (`set`) DO @echo %i
>
> and hit enter, the command window will just close down completely like I
> just issue the EXIT command.
>
> This only happen to
> FOR /F ["options"] %variable IN (`command`) DO command
> [command-parameters]
>
> If i just use the FOR to parse the content of a file, then everthing just
> work as expected.
>
> Anyone seen this kind of problem before?
>

Random Windows behaviour? It works here, but is there some reason you are
using usebackq?

FOR /F "delims==" %i IN ('set') DO @echo %i

On Fri, 26 Oct 2007 11:31:09 +0100, "Kok Yong Lee" <(E-Mail Removed)> wrote:

>Forgot to mention the Os is WinXp SP2
>
>"Kok Yong Lee" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed)...
>> hi there,
>>
>> I bumped into a weird machine in my office where in the command window
>> when I type in
>> FOR /F "usebackq delims==" %i IN (`set`) DO @echo %i
>>
>> and hit enter, the command window will just close down completely like I
>> just issue the EXIT command.
>>
>> This only happen to
>> FOR /F ["options"] %variable IN (`command`) DO command
>> [command-parameters]
>>
>> If i just use the FOR to parse the content of a file, then everthing just
>> work as expected.
>>
>> Anyone seen this kind of problem before?
>>
>

Not really, I only copy the exmapel command from FOR /? to try out.

It is the same behaviour as well for "FOR /F "delims==" %i IN ('set') DO
@echo %i"

It is definately weird ebahviour but not random as it is reproducible every
time.


"foxidrive" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> Random Windows behaviour? It works here, but is there some reason you are
> using usebackq?
>
> FOR /F "delims==" %i IN ('set') DO @echo %i
>
> On Fri, 26 Oct 2007 11:31:09 +0100, "Kok Yong Lee" <(E-Mail Removed)>
> wrote:
>
>>Forgot to mention the Os is WinXp SP2
>>
>>"Kok Yong Lee" <(E-Mail Removed)> wrote in message
>>news:(E-Mail Removed)...
>>> hi there,
>>>
>>> I bumped into a weird machine in my office where in the command window
>>> when I type in
>>> FOR /F "usebackq delims==" %i IN (`set`) DO @echo %i
>>>
>>> and hit enter, the command window will just close down completely like I
>>> just issue the EXIT command.
>>>
>>> This only happen to
>>> FOR /F ["options"] %variable IN (`command`) DO command
>>> [command-parameters]
>>>
>>> If i just use the FOR to parse the content of a file, then everthing
>>> just
>>> work as expected.
>>>
>>> Anyone seen this kind of problem before?
>>>
>>

Kok Yong Lee wrote:
> Not really, I only copy the exmapel command from FOR /? to try out.
>
> It is the same behaviour as well for "FOR /F "delims==" %i IN ('set') DO
> @echo %i"
>
> It is definately weird ebahviour but not random as it is reproducible every
> time.
>
>
> "foxidrive" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Random Windows behaviour? It works here, but is there some reason you are
>> using usebackq?
>>
>> FOR /F "delims==" %i IN ('set') DO @echo %i
>>
>> On Fri, 26 Oct 2007 11:31:09 +0100, "Kok Yong Lee" <(E-Mail Removed)>
>> wrote:
>>
>>> Forgot to mention the Os is WinXp SP2
>>>
>>> "Kok Yong Lee" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> hi there,
>>>>
>>>> I bumped into a weird machine in my office where in the command window
>>>> when I type in
>>>> FOR /F "usebackq delims==" %i IN (`set`) DO @echo %i
>>>>
>>>> and hit enter, the command window will just close down completely like I
>>>> just issue the EXIT command.
>>>>
>>>> This only happen to
>>>> FOR /F ["options"] %variable IN (`command`) DO command
>>>> [command-parameters]
>>>>
>>>> If i just use the FOR to parse the content of a file, then everthing
>>>> just
>>>> work as expected.
>>>>
>>>> Anyone seen this kind of problem before?
>>>>
>
>
Maybe a prank synonym of "set" to "For"?

Random in terms of different Windows installations can behave differently.
(There's an entire MS knowledgebase out there dedicated to those things...)

There is also a random behaviour in a CMD window at times which is fixed with a
reboot.

On Fri, 26 Oct 2007 11:56:53 +0100, "Kok Yong Lee" <(E-Mail Removed)> wrote:

>Not really, I only copy the exmapel command from FOR /? to try out.
>
>It is the same behaviour as well for "FOR /F "delims==" %i IN ('set') DO
>@echo %i"
>
>It is definately weird ebahviour but not random as it is reproducible every
>time.
>
>
>"foxidrive" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed)...
>>
>> Random Windows behaviour? It works here, but is there some reason you are
>> using usebackq?
>>
>> FOR /F "delims==" %i IN ('set') DO @echo %i