assign cmd variable to output of a for do loop
up vote
0
down vote
favorite
net accounts | for /f "tokens=3" %%a in ('find /I "computer role"') do echo %%a
This line does exactly what I want to know. However, I would like to assign the output of this command to a variable, then reference that variable later in the batch file. Suggestions?
batch-file
add a comment |
up vote
0
down vote
favorite
net accounts | for /f "tokens=3" %%a in ('find /I "computer role"') do echo %%a
This line does exactly what I want to know. However, I would like to assign the output of this command to a variable, then reference that variable later in the batch file. Suggestions?
batch-file
Same way you assigned the parsed output of theFOR
command to a variable in your question you asked yesterday.
– Squashman
Nov 8 at 3:27
yesterday's mess became: (set /p _build=<"C:Deploymentsdeploy.ver" & IF "!_build!"=="%_thisVer%" ) so that's working now.... Are you saying that I can "nest" for statements? Because I tried set /p _type=net accoun...... and it doesn't like it.
– G. Malsack
Nov 8 at 3:37
usebackq ;-)...
– G. Malsack
Nov 8 at 3:38
This was your code from yesterday:set build=%%F
. So what do you think you need to do with this code?
– Squashman
Nov 8 at 3:41
pastebin.com/Cu613UAG
– G. Malsack
Nov 8 at 3:58
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
net accounts | for /f "tokens=3" %%a in ('find /I "computer role"') do echo %%a
This line does exactly what I want to know. However, I would like to assign the output of this command to a variable, then reference that variable later in the batch file. Suggestions?
batch-file
net accounts | for /f "tokens=3" %%a in ('find /I "computer role"') do echo %%a
This line does exactly what I want to know. However, I would like to assign the output of this command to a variable, then reference that variable later in the batch file. Suggestions?
batch-file
batch-file
asked Nov 8 at 3:18
G. Malsack
53
53
Same way you assigned the parsed output of theFOR
command to a variable in your question you asked yesterday.
– Squashman
Nov 8 at 3:27
yesterday's mess became: (set /p _build=<"C:Deploymentsdeploy.ver" & IF "!_build!"=="%_thisVer%" ) so that's working now.... Are you saying that I can "nest" for statements? Because I tried set /p _type=net accoun...... and it doesn't like it.
– G. Malsack
Nov 8 at 3:37
usebackq ;-)...
– G. Malsack
Nov 8 at 3:38
This was your code from yesterday:set build=%%F
. So what do you think you need to do with this code?
– Squashman
Nov 8 at 3:41
pastebin.com/Cu613UAG
– G. Malsack
Nov 8 at 3:58
add a comment |
Same way you assigned the parsed output of theFOR
command to a variable in your question you asked yesterday.
– Squashman
Nov 8 at 3:27
yesterday's mess became: (set /p _build=<"C:Deploymentsdeploy.ver" & IF "!_build!"=="%_thisVer%" ) so that's working now.... Are you saying that I can "nest" for statements? Because I tried set /p _type=net accoun...... and it doesn't like it.
– G. Malsack
Nov 8 at 3:37
usebackq ;-)...
– G. Malsack
Nov 8 at 3:38
This was your code from yesterday:set build=%%F
. So what do you think you need to do with this code?
– Squashman
Nov 8 at 3:41
pastebin.com/Cu613UAG
– G. Malsack
Nov 8 at 3:58
Same way you assigned the parsed output of the
FOR
command to a variable in your question you asked yesterday.– Squashman
Nov 8 at 3:27
Same way you assigned the parsed output of the
FOR
command to a variable in your question you asked yesterday.– Squashman
Nov 8 at 3:27
yesterday's mess became: (set /p _build=<"C:Deploymentsdeploy.ver" & IF "!_build!"=="%_thisVer%" ) so that's working now.... Are you saying that I can "nest" for statements? Because I tried set /p _type=net accoun...... and it doesn't like it.
– G. Malsack
Nov 8 at 3:37
yesterday's mess became: (set /p _build=<"C:Deploymentsdeploy.ver" & IF "!_build!"=="%_thisVer%" ) so that's working now.... Are you saying that I can "nest" for statements? Because I tried set /p _type=net accoun...... and it doesn't like it.
– G. Malsack
Nov 8 at 3:37
usebackq ;-)...
– G. Malsack
Nov 8 at 3:38
usebackq ;-)...
– G. Malsack
Nov 8 at 3:38
This was your code from yesterday:
set build=%%F
. So what do you think you need to do with this code?– Squashman
Nov 8 at 3:41
This was your code from yesterday:
set build=%%F
. So what do you think you need to do with this code?– Squashman
Nov 8 at 3:41
pastebin.com/Cu613UAG
– G. Malsack
Nov 8 at 3:58
pastebin.com/Cu613UAG
– G. Malsack
Nov 8 at 3:58
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
The SET
command is used to assign variables.
@echo off
for /f "tokens=3" %%a in ('net accounts ^|find /I "computer role"') do set role=%%a
echo role=%role%
pause
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
The SET
command is used to assign variables.
@echo off
for /f "tokens=3" %%a in ('net accounts ^|find /I "computer role"') do set role=%%a
echo role=%role%
pause
add a comment |
up vote
0
down vote
accepted
The SET
command is used to assign variables.
@echo off
for /f "tokens=3" %%a in ('net accounts ^|find /I "computer role"') do set role=%%a
echo role=%role%
pause
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
The SET
command is used to assign variables.
@echo off
for /f "tokens=3" %%a in ('net accounts ^|find /I "computer role"') do set role=%%a
echo role=%role%
pause
The SET
command is used to assign variables.
@echo off
for /f "tokens=3" %%a in ('net accounts ^|find /I "computer role"') do set role=%%a
echo role=%role%
pause
answered Nov 8 at 3:47
Squashman
8,18331932
8,18331932
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53201068%2fassign-cmd-variable-to-output-of-a-for-do-loop%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Same way you assigned the parsed output of the
FOR
command to a variable in your question you asked yesterday.– Squashman
Nov 8 at 3:27
yesterday's mess became: (set /p _build=<"C:Deploymentsdeploy.ver" & IF "!_build!"=="%_thisVer%" ) so that's working now.... Are you saying that I can "nest" for statements? Because I tried set /p _type=net accoun...... and it doesn't like it.
– G. Malsack
Nov 8 at 3:37
usebackq ;-)...
– G. Malsack
Nov 8 at 3:38
This was your code from yesterday:
set build=%%F
. So what do you think you need to do with this code?– Squashman
Nov 8 at 3:41
pastebin.com/Cu613UAG
– G. Malsack
Nov 8 at 3:58