“Variabilize” the ampersand (background a process)












7















I want to know if there's a way to put the ampersand in a variable and still use it to send a process to the background.



This works:



BCKGRND=yes

if [ "$BCKGRND" = "yes" ]; then

    sleep 5 &

else

    sleep 5

fi


But wouldn't it be cool to accomplish those five lines with only one? Like so:



BCKGRND='&'

sleep 5 ${BCKGRND}


But that doesn't work. If BCKGRND isn't set it works - but when it is set it's interpreted it as a literal '&' and errors out.






bash shell-script variable background-process







share|improve this question









New contributor




BrowncoatOkie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    7















    I want to know if there's a way to put the ampersand in a variable and still use it to send a process to the background.



    This works:



    BCKGRND=yes
    
if [ "$BCKGRND" = "yes" ]; then
    
    sleep 5 &
    
else
    
    sleep 5
    
fi


    But wouldn't it be cool to accomplish those five lines with only one? Like so:



    BCKGRND='&'
    
sleep 5 ${BCKGRND}


    But that doesn't work. If BCKGRND isn't set it works - but when it is set it's interpreted it as a literal '&' and errors out.






    bash shell-script variable background-process







    share|improve this question









    New contributor




    BrowncoatOkie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      7












      7








      7








      I want to know if there's a way to put the ampersand in a variable and still use it to send a process to the background.



      This works:



      BCKGRND=yes
      
if [ "$BCKGRND" = "yes" ]; then
      
    sleep 5 &
      
else
      
    sleep 5
      
fi


      But wouldn't it be cool to accomplish those five lines with only one? Like so:



      BCKGRND='&'
      
sleep 5 ${BCKGRND}


      But that doesn't work. If BCKGRND isn't set it works - but when it is set it's interpreted it as a literal '&' and errors out.






      bash shell-script variable background-process







      share|improve this question









      New contributor




      BrowncoatOkie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I want to know if there's a way to put the ampersand in a variable and still use it to send a process to the background.



      This works:



      BCKGRND=yes
      
if [ "$BCKGRND" = "yes" ]; then
      
    sleep 5 &
      
else
      
    sleep 5
      
fi


      But wouldn't it be cool to accomplish those five lines with only one? Like so:



      BCKGRND='&'
      
sleep 5 ${BCKGRND}


      But that doesn't work. If BCKGRND isn't set it works - but when it is set it's interpreted it as a literal '&' and errors out.






      bash shell-script variable background-process




      bash shell-script variable background-process






      share|improve this question









      New contributor




      BrowncoatOkie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      BrowncoatOkie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited 2 days ago









      Stephen Kitt

      166k24367447




      166k24367447






      New contributor




      BrowncoatOkie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 2 days ago









      BrowncoatOkieBrowncoatOkie

      464




      464




      New contributor




      BrowncoatOkie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      BrowncoatOkie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      BrowncoatOkie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          3 Answers
          3






          active

          oldest

          votes


















          8














          It's not possible to use a variable to background the call because variable expansion happens after the command-line is parsed for control operators (such as && and &).



          Yet another option would be to wrap the calls in a function:



          mayberunbg() {
          
  if [ "$BCKGRND" = "yes" ]; then
          
    "$@" &
          
  else
          
    "$@"
          
  fi
          
}


          ... and then set the variable as needed:



          $ BCKGRND=yes mayberunbg sleep 3
          
[1] 14137
          
$
          
[1]+  Done                    "$@"
          
# or
          
$ BCKGRND=yes
          
$ mayberunbg sleep 3
          
[1] 14203
          
$
          
[1]+  Done                    "$@"
          
$ BCKGRND=no mayberunbg sleep 3
          
# 3 seconds later
          
$





          share|improve this answer
























          • What, no ed? +1 anyway, this is the cleanest solution.

            – Stephen Kitt
            2 days ago













          • LOL @StephenKitt; now the gears are turning

            – Jeff Schaller
            2 days ago











          • I liked the eval answer for its simplicity but my actual real-world command I wanted to background was far too complicated with too many variables in it to be comfortable using eval. @jeff-schaller gave the answer that pointed me in the direction I went. Instead of a function, though, I put the entire command in a variable then used his if statement style to execute the command with or without the &.

            – BrowncoatOkie
            2 days ago



















          10














          You can flip things and variabilise “foregrounding”:



          FOREGROUND=fg
          
sleep 5 & ${FOREGROUND}


          Set FOREGROUND to true or empty to run the process in the background. (Setting FOREGROUND to true to run in the background is admittedly confusing! Appropriate variable names are left as an exercise for the reader.)






          share|improve this answer



















          • 4





            that's nice but it won't work in a shell without job control (ie any script unless set -m was used).

            – mosvy
            2 days ago



















          8














          You would probably have to use eval:



          eval "sleep 5" "$BCKGRND"


          eval causes the shell to re-evaluate the arguments given. A literal & would therefore be interpreted as & at the end of a command and not as an argument to the command, putting the command in the background.






          share|improve this answer





















          • 1





            A answer containing eval should contain a warning, that this should be handles with care. See e.g. this answer.

            – Ralf
            2 days ago











          • I don't get what the problem is with "$BCKGRND" evaluating to an empty argument.

            – mosvy
            2 days ago






          • 2





            @Ralf absolutely irrelevant in this case. There's nothing special about eval -- you can execute commands via arithmetic expansions, for instance. Maybe there should be such a warning against using bash (or any similar shell) at all ;-)

            – mosvy
            2 days ago






          • 1





            @Kusalananda eval will join its arguments with spaces before doing the actual eval. Just try it: eval printf "'{%s}n'" foo "" "" "". eval foo "" "" "" "" is completely similar to eval foo, no matter what IFS or other thing is.

            – mosvy
            2 days ago








          • 1





            The command being eval'ed should be in double quotes if it contains any special characters, e.g. eval 'sleep $TIMEOUT' "$BACKGROUND". Otherwise you could get double expansions if the variable expands to another variable or contains special characters. Also, nested quoting can get tricky.

            – Barmar
            2 days ago











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          BrowncoatOkie is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493464%2fvariabilize-the-ampersand-background-a-process%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          3 Answers
          3






          active

          oldest

          votes








          3 Answers
          3






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          8














          It's not possible to use a variable to background the call because variable expansion happens after the command-line is parsed for control operators (such as && and &).



          Yet another option would be to wrap the calls in a function:



          mayberunbg() {
          
  if [ "$BCKGRND" = "yes" ]; then
          
    "$@" &
          
  else
          
    "$@"
          
  fi
          
}


          ... and then set the variable as needed:



          $ BCKGRND=yes mayberunbg sleep 3
          
[1] 14137
          
$
          
[1]+  Done                    "$@"
          
# or
          
$ BCKGRND=yes
          
$ mayberunbg sleep 3
          
[1] 14203
          
$
          
[1]+  Done                    "$@"
          
$ BCKGRND=no mayberunbg sleep 3
          
# 3 seconds later
          
$





          share|improve this answer
























          • What, no ed? +1 anyway, this is the cleanest solution.

            – Stephen Kitt
            2 days ago













          • LOL @StephenKitt; now the gears are turning

            – Jeff Schaller
            2 days ago











          • I liked the eval answer for its simplicity but my actual real-world command I wanted to background was far too complicated with too many variables in it to be comfortable using eval. @jeff-schaller gave the answer that pointed me in the direction I went. Instead of a function, though, I put the entire command in a variable then used his if statement style to execute the command with or without the &.

            – BrowncoatOkie
            2 days ago
















          8














          It's not possible to use a variable to background the call because variable expansion happens after the command-line is parsed for control operators (such as && and &).



          Yet another option would be to wrap the calls in a function:



          mayberunbg() {
          
  if [ "$BCKGRND" = "yes" ]; then
          
    "$@" &
          
  else
          
    "$@"
          
  fi
          
}


          ... and then set the variable as needed:



          $ BCKGRND=yes mayberunbg sleep 3
          
[1] 14137
          
$
          
[1]+  Done                    "$@"
          
# or
          
$ BCKGRND=yes
          
$ mayberunbg sleep 3
          
[1] 14203
          
$
          
[1]+  Done                    "$@"
          
$ BCKGRND=no mayberunbg sleep 3
          
# 3 seconds later
          
$





          share|improve this answer
























          • What, no ed? +1 anyway, this is the cleanest solution.

            – Stephen Kitt
            2 days ago













          • LOL @StephenKitt; now the gears are turning

            – Jeff Schaller
            2 days ago











          • I liked the eval answer for its simplicity but my actual real-world command I wanted to background was far too complicated with too many variables in it to be comfortable using eval. @jeff-schaller gave the answer that pointed me in the direction I went. Instead of a function, though, I put the entire command in a variable then used his if statement style to execute the command with or without the &.

            – BrowncoatOkie
            2 days ago














          8












          8








          8







          It's not possible to use a variable to background the call because variable expansion happens after the command-line is parsed for control operators (such as && and &).



          Yet another option would be to wrap the calls in a function:



          mayberunbg() {
          
  if [ "$BCKGRND" = "yes" ]; then
          
    "$@" &
          
  else
          
    "$@"
          
  fi
          
}


          ... and then set the variable as needed:



          $ BCKGRND=yes mayberunbg sleep 3
          
[1] 14137
          
$
          
[1]+  Done                    "$@"
          
# or
          
$ BCKGRND=yes
          
$ mayberunbg sleep 3
          
[1] 14203
          
$
          
[1]+  Done                    "$@"
          
$ BCKGRND=no mayberunbg sleep 3
          
# 3 seconds later
          
$





          share|improve this answer













          It's not possible to use a variable to background the call because variable expansion happens after the command-line is parsed for control operators (such as && and &).



          Yet another option would be to wrap the calls in a function:



          mayberunbg() {
          
  if [ "$BCKGRND" = "yes" ]; then
          
    "$@" &
          
  else
          
    "$@"
          
  fi
          
}


          ... and then set the variable as needed:



          $ BCKGRND=yes mayberunbg sleep 3
          
[1] 14137
          
$
          
[1]+  Done                    "$@"
          
# or
          
$ BCKGRND=yes
          
$ mayberunbg sleep 3
          
[1] 14203
          
$
          
[1]+  Done                    "$@"
          
$ BCKGRND=no mayberunbg sleep 3
          
# 3 seconds later
          
$






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 2 days ago









          Jeff SchallerJeff Schaller

          39.3k1054125




          39.3k1054125













          • What, no ed? +1 anyway, this is the cleanest solution.

            – Stephen Kitt
            2 days ago













          • LOL @StephenKitt; now the gears are turning

            – Jeff Schaller
            2 days ago











          • I liked the eval answer for its simplicity but my actual real-world command I wanted to background was far too complicated with too many variables in it to be comfortable using eval. @jeff-schaller gave the answer that pointed me in the direction I went. Instead of a function, though, I put the entire command in a variable then used his if statement style to execute the command with or without the &.

            – BrowncoatOkie
            2 days ago



















          • What, no ed? +1 anyway, this is the cleanest solution.

            – Stephen Kitt
            2 days ago













          • LOL @StephenKitt; now the gears are turning

            – Jeff Schaller
            2 days ago











          • I liked the eval answer for its simplicity but my actual real-world command I wanted to background was far too complicated with too many variables in it to be comfortable using eval. @jeff-schaller gave the answer that pointed me in the direction I went. Instead of a function, though, I put the entire command in a variable then used his if statement style to execute the command with or without the &.

            – BrowncoatOkie
            2 days ago

















          What, no ed? +1 anyway, this is the cleanest solution.

          – Stephen Kitt
          2 days ago







          What, no ed? +1 anyway, this is the cleanest solution.

          – Stephen Kitt
          2 days ago















          LOL @StephenKitt; now the gears are turning

          – Jeff Schaller
          2 days ago





          LOL @StephenKitt; now the gears are turning

          – Jeff Schaller
          2 days ago













          I liked the eval answer for its simplicity but my actual real-world command I wanted to background was far too complicated with too many variables in it to be comfortable using eval. @jeff-schaller gave the answer that pointed me in the direction I went. Instead of a function, though, I put the entire command in a variable then used his if statement style to execute the command with or without the &.

          – BrowncoatOkie
          2 days ago





          I liked the eval answer for its simplicity but my actual real-world command I wanted to background was far too complicated with too many variables in it to be comfortable using eval. @jeff-schaller gave the answer that pointed me in the direction I went. Instead of a function, though, I put the entire command in a variable then used his if statement style to execute the command with or without the &.

          – BrowncoatOkie
          2 days ago













          10














          You can flip things and variabilise “foregrounding”:



          FOREGROUND=fg
          
sleep 5 & ${FOREGROUND}


          Set FOREGROUND to true or empty to run the process in the background. (Setting FOREGROUND to true to run in the background is admittedly confusing! Appropriate variable names are left as an exercise for the reader.)






          share|improve this answer



















          • 4





            that's nice but it won't work in a shell without job control (ie any script unless set -m was used).

            – mosvy
            2 days ago
















          10














          You can flip things and variabilise “foregrounding”:



          FOREGROUND=fg
          
sleep 5 & ${FOREGROUND}


          Set FOREGROUND to true or empty to run the process in the background. (Setting FOREGROUND to true to run in the background is admittedly confusing! Appropriate variable names are left as an exercise for the reader.)






          share|improve this answer



















          • 4





            that's nice but it won't work in a shell without job control (ie any script unless set -m was used).

            – mosvy
            2 days ago














          10












          10








          10







          You can flip things and variabilise “foregrounding”:



          FOREGROUND=fg
          
sleep 5 & ${FOREGROUND}


          Set FOREGROUND to true or empty to run the process in the background. (Setting FOREGROUND to true to run in the background is admittedly confusing! Appropriate variable names are left as an exercise for the reader.)






          share|improve this answer













          You can flip things and variabilise “foregrounding”:



          FOREGROUND=fg
          
sleep 5 & ${FOREGROUND}


          Set FOREGROUND to true or empty to run the process in the background. (Setting FOREGROUND to true to run in the background is admittedly confusing! Appropriate variable names are left as an exercise for the reader.)







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 2 days ago









          Stephen KittStephen Kitt

          166k24367447




          166k24367447








          • 4





            that's nice but it won't work in a shell without job control (ie any script unless set -m was used).

            – mosvy
            2 days ago














          • 4





            that's nice but it won't work in a shell without job control (ie any script unless set -m was used).

            – mosvy
            2 days ago








          4




          4





          that's nice but it won't work in a shell without job control (ie any script unless set -m was used).

          – mosvy
          2 days ago





          that's nice but it won't work in a shell without job control (ie any script unless set -m was used).

          – mosvy
          2 days ago











          8














          You would probably have to use eval:



          eval "sleep 5" "$BCKGRND"


          eval causes the shell to re-evaluate the arguments given. A literal & would therefore be interpreted as & at the end of a command and not as an argument to the command, putting the command in the background.






          share|improve this answer





















          • 1





            A answer containing eval should contain a warning, that this should be handles with care. See e.g. this answer.

            – Ralf
            2 days ago











          • I don't get what the problem is with "$BCKGRND" evaluating to an empty argument.

            – mosvy
            2 days ago






          • 2





            @Ralf absolutely irrelevant in this case. There's nothing special about eval -- you can execute commands via arithmetic expansions, for instance. Maybe there should be such a warning against using bash (or any similar shell) at all ;-)

            – mosvy
            2 days ago






          • 1





            @Kusalananda eval will join its arguments with spaces before doing the actual eval. Just try it: eval printf "'{%s}n'" foo "" "" "". eval foo "" "" "" "" is completely similar to eval foo, no matter what IFS or other thing is.

            – mosvy
            2 days ago








          • 1





            The command being eval'ed should be in double quotes if it contains any special characters, e.g. eval 'sleep $TIMEOUT' "$BACKGROUND". Otherwise you could get double expansions if the variable expands to another variable or contains special characters. Also, nested quoting can get tricky.

            – Barmar
            2 days ago
















          8














          You would probably have to use eval:



          eval "sleep 5" "$BCKGRND"


          eval causes the shell to re-evaluate the arguments given. A literal & would therefore be interpreted as & at the end of a command and not as an argument to the command, putting the command in the background.






          share|improve this answer





















          • 1





            A answer containing eval should contain a warning, that this should be handles with care. See e.g. this answer.

            – Ralf
            2 days ago











          • I don't get what the problem is with "$BCKGRND" evaluating to an empty argument.

            – mosvy
            2 days ago






          • 2





            @Ralf absolutely irrelevant in this case. There's nothing special about eval -- you can execute commands via arithmetic expansions, for instance. Maybe there should be such a warning against using bash (or any similar shell) at all ;-)

            – mosvy
            2 days ago






          • 1





            @Kusalananda eval will join its arguments with spaces before doing the actual eval. Just try it: eval printf "'{%s}n'" foo "" "" "". eval foo "" "" "" "" is completely similar to eval foo, no matter what IFS or other thing is.

            – mosvy
            2 days ago








          • 1





            The command being eval'ed should be in double quotes if it contains any special characters, e.g. eval 'sleep $TIMEOUT' "$BACKGROUND". Otherwise you could get double expansions if the variable expands to another variable or contains special characters. Also, nested quoting can get tricky.

            – Barmar
            2 days ago














          8












          8








          8







          You would probably have to use eval:



          eval "sleep 5" "$BCKGRND"


          eval causes the shell to re-evaluate the arguments given. A literal & would therefore be interpreted as & at the end of a command and not as an argument to the command, putting the command in the background.






          share|improve this answer















          You would probably have to use eval:



          eval "sleep 5" "$BCKGRND"


          eval causes the shell to re-evaluate the arguments given. A literal & would therefore be interpreted as & at the end of a command and not as an argument to the command, putting the command in the background.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 2 days ago

























          answered 2 days ago









          KusalanandaKusalananda

          123k16232381




          123k16232381








          • 1





            A answer containing eval should contain a warning, that this should be handles with care. See e.g. this answer.

            – Ralf
            2 days ago











          • I don't get what the problem is with "$BCKGRND" evaluating to an empty argument.

            – mosvy
            2 days ago






          • 2





            @Ralf absolutely irrelevant in this case. There's nothing special about eval -- you can execute commands via arithmetic expansions, for instance. Maybe there should be such a warning against using bash (or any similar shell) at all ;-)

            – mosvy
            2 days ago






          • 1





            @Kusalananda eval will join its arguments with spaces before doing the actual eval. Just try it: eval printf "'{%s}n'" foo "" "" "". eval foo "" "" "" "" is completely similar to eval foo, no matter what IFS or other thing is.

            – mosvy
            2 days ago








          • 1





            The command being eval'ed should be in double quotes if it contains any special characters, e.g. eval 'sleep $TIMEOUT' "$BACKGROUND". Otherwise you could get double expansions if the variable expands to another variable or contains special characters. Also, nested quoting can get tricky.

            – Barmar
            2 days ago














          • 1





            A answer containing eval should contain a warning, that this should be handles with care. See e.g. this answer.

            – Ralf
            2 days ago











          • I don't get what the problem is with "$BCKGRND" evaluating to an empty argument.

            – mosvy
            2 days ago






          • 2





            @Ralf absolutely irrelevant in this case. There's nothing special about eval -- you can execute commands via arithmetic expansions, for instance. Maybe there should be such a warning against using bash (or any similar shell) at all ;-)

            – mosvy
            2 days ago






          • 1





            @Kusalananda eval will join its arguments with spaces before doing the actual eval. Just try it: eval printf "'{%s}n'" foo "" "" "". eval foo "" "" "" "" is completely similar to eval foo, no matter what IFS or other thing is.

            – mosvy
            2 days ago








          • 1





            The command being eval'ed should be in double quotes if it contains any special characters, e.g. eval 'sleep $TIMEOUT' "$BACKGROUND". Otherwise you could get double expansions if the variable expands to another variable or contains special characters. Also, nested quoting can get tricky.

            – Barmar
            2 days ago








          1




          1





          A answer containing eval should contain a warning, that this should be handles with care. See e.g. this answer.

          – Ralf
          2 days ago





          A answer containing eval should contain a warning, that this should be handles with care. See e.g. this answer.

          – Ralf
          2 days ago













          I don't get what the problem is with "$BCKGRND" evaluating to an empty argument.

          – mosvy
          2 days ago





          I don't get what the problem is with "$BCKGRND" evaluating to an empty argument.

          – mosvy
          2 days ago




          2




          2





          @Ralf absolutely irrelevant in this case. There's nothing special about eval -- you can execute commands via arithmetic expansions, for instance. Maybe there should be such a warning against using bash (or any similar shell) at all ;-)

          – mosvy
          2 days ago





          @Ralf absolutely irrelevant in this case. There's nothing special about eval -- you can execute commands via arithmetic expansions, for instance. Maybe there should be such a warning against using bash (or any similar shell) at all ;-)

          – mosvy
          2 days ago




          1




          1





          @Kusalananda eval will join its arguments with spaces before doing the actual eval. Just try it: eval printf "'{%s}n'" foo "" "" "". eval foo "" "" "" "" is completely similar to eval foo, no matter what IFS or other thing is.

          – mosvy
          2 days ago







          @Kusalananda eval will join its arguments with spaces before doing the actual eval. Just try it: eval printf "'{%s}n'" foo "" "" "". eval foo "" "" "" "" is completely similar to eval foo, no matter what IFS or other thing is.

          – mosvy
          2 days ago






          1




          1





          The command being eval'ed should be in double quotes if it contains any special characters, e.g. eval 'sleep $TIMEOUT' "$BACKGROUND". Otherwise you could get double expansions if the variable expands to another variable or contains special characters. Also, nested quoting can get tricky.

          – Barmar
          2 days ago





          The command being eval'ed should be in double quotes if it contains any special characters, e.g. eval 'sleep $TIMEOUT' "$BACKGROUND". Otherwise you could get double expansions if the variable expands to another variable or contains special characters. Also, nested quoting can get tricky.

          – Barmar
          2 days ago










          BrowncoatOkie is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          BrowncoatOkie is a new contributor. Be nice, and check out our Code of Conduct.













          BrowncoatOkie is a new contributor. Be nice, and check out our Code of Conduct.












          BrowncoatOkie is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • 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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493464%2fvariabilize-the-ampersand-background-a-process%23new-answer', 'question_page');
          }
          );

          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







          -

          Popular posts from this blog

          Сан-Квентин

          Image
          Сан-Квентин Местоположение Сан-Квентин, Калифорния Координаты 37°56′13″ с. ш. 122°29′20″ з. д. H G Я O L Текущий статус Действует Режим безопасности минимальный и максимальный Количество мест 3 302 Открытие Июнь 1852 Находится в ведомстве California Department of Corrections and Rehabilitation Начальник Mike Martel, начальник  Сан-Квентин на Викискладе Сан-Квентин (англ.  San Quentin ) — тюрьма, располагающаяся на 432 акрах (около 1,7 км²), на мысе Сан-Квентин, в округе Марин, штат Калифорния, США. Тюрьма штата Калифорния Сан-Квентин была открыта в июле 1852 года и является старейшей в штате. Она была построена заключёнными, которые проживали в течение строительства на тюремном судне Вабан. В Сан-Квентине отбывали наказание и мужчины, и женщины до 1934 года, когда построили женскую тюрьму в Техачапи и туда перевели всех заключённых женщин. В Сан-Квентине приводятся в исполнение смертные казни, для этого имеется газовая камера, но...
          Read more

          8-я гвардейская общевойсковая армия

          Image
          8-я гвардейская общевойсковая ордена Ленина армия Награды: Войска: РККА → Советская армия → СВ России Род войск: Формирование: 1943 Расформирование (преобразование): 1992 Предшественник: 62-я армия (1942—43) → 8-я гвардейская общевойсковая армия (1943—92) → 8-й гвардейский армейский корпус (1992—98) Боевой путь Изюм-Барвенковская операция Донбасская операция Запорожская операция Битва за Днепр Днепропетровская операция Березнеговато-Снигирёвская операция Одесская операция Люблин-Брестская операция Варшавско-Познанская операция Восточно-Померанская операция Берлинская наступательная операция У этого термина существуют и другие значения, см. 8-я армия. Фотография Гвардейского Красного Знамени (лицевая сторона) 8-й гвардейской армии , образца 1943 года. Фотография Гвардейского Красного Знамени (оборотная сторона) 8-й гвардейской армии , образца 1943 года. 8-я гвардейская общевойсковая ордена Ленина армия  — гвардейское фор...
          Read more

          Алькесар

          Image
          Муниципалитет Алькесар Alquézar Герб 42°10′16″ с. ш. 0°01′27″ в. д. H G Я O L Страна Испания   Испания Автономное сообщество Арагон Провинция Уэска Комарка Сомонтано-де-Барбастро Алькальд Хосе Марияно Альтемир Ласкорс (ИСРП) История и география Площадь 32,36 км² Высота НУМ 660 м Часовой пояс UTC+1, летом UTC+2 Население Население 313 человек ( 2010 ) Плотность 9,92 чел./км² Этнохороним alquezarano/-a Цифровые идентификаторы Телефонный код +34 974 Почтовые индексы 22112 Автомобильный код HU alquezar.org   (исп.) Показать/скрыть карты Алькесар Алькесар Алькесар  Аудио, фото и видео на Викискладе Алькесар (исп.  Alquézar ) — муниципалитет в Испании, входит в провинцию Уэска, в составе автономного сообщества Арагон. Муниципалитет находится в составе района (комарки) Сомонтано-де-Барбастро. Занимает площадь 32,36 км². Население — 321 челове...
          Read more