How to spawn a new terminal windows from shell and the use it as default? [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
I am trying to write a bash script that spawns a new terminal window and use this spawned window as default for executing all other commands in the script.
Is that possible? I'm using Roxterm and stumbled across the -e switch, that lets one execute one command in the spawned terminal, but I didn't find a switch that uses the spawned window as default.
linux bash scripting
asked Jul 28 at 7:54
t3ngu
333
closed as unclear what you're asking by Kusalananda, schily, Thomas, Romeo Ninov, steve Jul 29 at 22:01
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
up vote
1
down vote
favorite
I am trying to write a bash script that spawns a new terminal window and use this spawned window as default for executing all other commands in the script.
Is that possible? I'm using Roxterm and stumbled across the -e switch, that lets one execute one command in the spawned terminal, but I didn't find a switch that uses the spawned window as default.
linux bash scripting
asked Jul 28 at 7:54
t3ngu
333
closed as unclear what you're asking by Kusalananda, schily, Thomas, Romeo Ninov, steve Jul 29 at 22:01
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
the spawned window as input or output? or both at some point? the script file is what is read for commands executed in a script file, typically, but your-ecould prefixENV=scriptfile shor something
– mikeserv
Jul 28 at 8:01
I forgot, yes, both. The scriptfile should launch a new terminal window with specific geometry (--geometry) and should be fully interactive. The original scriptfile should only provide the commands to be exceuted, but in- and output should be completely via the spawned terminal window.
– t3ngu
Jul 28 at 8:14
huh? the scriptfile should... provide commands... but [i/o] ... completely via spawned terminal... thats where you lose me. is the new terminal window accepting commands from scriptfile and live input? round-robin then? or do you want to script the launch of an interactive program&waitfor itsreturn$? until... doing more stuff?
– mikeserv
Jul 28 at 8:23
Make the script check for an argument first. If there's no argument, launch a terminal to run the same script (itself) but WITH an argument, and then exit. If there is an argument, skip launching a terminal and run the other commands.
– Thomas Zwaagstra
Jul 28 at 8:41
It's unclear if you want to write a script that starts a terminal with an interactive shell ("fully interactive"), or whether you want to execute a single non-interactive command, script or part of a script in the terminal. An example of what you are trying to do would be nice.
– Kusalananda
Jul 29 at 7:44
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am trying to write a bash script that spawns a new terminal window and use this spawned window as default for executing all other commands in the script.
Is that possible? I'm using Roxterm and stumbled across the -e switch, that lets one execute one command in the spawned terminal, but I didn't find a switch that uses the spawned window as default.
linux bash scripting
asked Jul 28 at 7:54
t3ngu
333
I am trying to write a bash script that spawns a new terminal window and use this spawned window as default for executing all other commands in the script.
Is that possible? I'm using Roxterm and stumbled across the -e switch, that lets one execute one command in the spawned terminal, but I didn't find a switch that uses the spawned window as default.
linux bash scripting
asked Jul 28 at 7:54
t3ngu
333
asked Jul 28 at 7:54
t3ngu
333
asked Jul 28 at 7:54
t3ngu
333
asked Jul 28 at 7:54
t3ngu
333
333
closed as unclear what you're asking by Kusalananda, schily, Thomas, Romeo Ninov, steve Jul 29 at 22:01
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as unclear what you're asking by Kusalananda, schily, Thomas, Romeo Ninov, steve Jul 29 at 22:01
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
the spawned window as input or output? or both at some point? the script file is what is read for commands executed in a script file, typically, but your-ecould prefixENV=scriptfile shor something
– mikeserv
Jul 28 at 8:01
I forgot, yes, both. The scriptfile should launch a new terminal window with specific geometry (--geometry) and should be fully interactive. The original scriptfile should only provide the commands to be exceuted, but in- and output should be completely via the spawned terminal window.
– t3ngu
Jul 28 at 8:14
huh? the scriptfile should... provide commands... but [i/o] ... completely via spawned terminal... thats where you lose me. is the new terminal window accepting commands from scriptfile and live input? round-robin then? or do you want to script the launch of an interactive program&waitfor itsreturn$? until... doing more stuff?
– mikeserv
Jul 28 at 8:23
Make the script check for an argument first. If there's no argument, launch a terminal to run the same script (itself) but WITH an argument, and then exit. If there is an argument, skip launching a terminal and run the other commands.
– Thomas Zwaagstra
Jul 28 at 8:41
It's unclear if you want to write a script that starts a terminal with an interactive shell ("fully interactive"), or whether you want to execute a single non-interactive command, script or part of a script in the terminal. An example of what you are trying to do would be nice.
– Kusalananda
Jul 29 at 7:44
add a comment |Â
the spawned window as input or output? or both at some point? the script file is what is read for commands executed in a script file, typically, but your-ecould prefixENV=scriptfile shor something
– mikeserv
Jul 28 at 8:01
I forgot, yes, both. The scriptfile should launch a new terminal window with specific geometry (--geometry) and should be fully interactive. The original scriptfile should only provide the commands to be exceuted, but in- and output should be completely via the spawned terminal window.
– t3ngu
Jul 28 at 8:14
huh? the scriptfile should... provide commands... but [i/o] ... completely via spawned terminal... thats where you lose me. is the new terminal window accepting commands from scriptfile and live input? round-robin then? or do you want to script the launch of an interactive program&waitfor itsreturn$? until... doing more stuff?
– mikeserv
Jul 28 at 8:23
Make the script check for an argument first. If there's no argument, launch a terminal to run the same script (itself) but WITH an argument, and then exit. If there is an argument, skip launching a terminal and run the other commands.
– Thomas Zwaagstra
Jul 28 at 8:41
It's unclear if you want to write a script that starts a terminal with an interactive shell ("fully interactive"), or whether you want to execute a single non-interactive command, script or part of a script in the terminal. An example of what you are trying to do would be nice.
– Kusalananda
Jul 29 at 7:44
the spawned window as input or output? or both at some point? the script file is what is read for commands executed in a script file, typically, but your
-e could prefix ENV=scriptfile sh or something– mikeserv
Jul 28 at 8:01
the spawned window as input or output? or both at some point? the script file is what is read for commands executed in a script file, typically, but your
-e could prefix ENV=scriptfile sh or something– mikeserv
Jul 28 at 8:01
I forgot, yes, both. The scriptfile should launch a new terminal window with specific geometry (--geometry) and should be fully interactive. The original scriptfile should only provide the commands to be exceuted, but in- and output should be completely via the spawned terminal window.
– t3ngu
Jul 28 at 8:14
I forgot, yes, both. The scriptfile should launch a new terminal window with specific geometry (--geometry) and should be fully interactive. The original scriptfile should only provide the commands to be exceuted, but in- and output should be completely via the spawned terminal window.
– t3ngu
Jul 28 at 8:14
huh? the scriptfile should... provide commands... but [i/o] ... completely via spawned terminal... thats where you lose me. is the new terminal window accepting commands from scriptfile and live input? round-robin then? or do you want to script the launch of an interactive program
&wait for its return$? until... doing more stuff?– mikeserv
Jul 28 at 8:23
huh? the scriptfile should... provide commands... but [i/o] ... completely via spawned terminal... thats where you lose me. is the new terminal window accepting commands from scriptfile and live input? round-robin then? or do you want to script the launch of an interactive program
&wait for its return$? until... doing more stuff?– mikeserv
Jul 28 at 8:23
Make the script check for an argument first. If there's no argument, launch a terminal to run the same script (itself) but WITH an argument, and then exit. If there is an argument, skip launching a terminal and run the other commands.
– Thomas Zwaagstra
Jul 28 at 8:41
Make the script check for an argument first. If there's no argument, launch a terminal to run the same script (itself) but WITH an argument, and then exit. If there is an argument, skip launching a terminal and run the other commands.
– Thomas Zwaagstra
Jul 28 at 8:41
It's unclear if you want to write a script that starts a terminal with an interactive shell ("fully interactive"), or whether you want to execute a single non-interactive command, script or part of a script in the terminal. An example of what you are trying to do would be nice.
– Kusalananda
Jul 29 at 7:44
It's unclear if you want to write a script that starts a terminal with an interactive shell ("fully interactive"), or whether you want to execute a single non-interactive command, script or part of a script in the terminal. An example of what you are trying to do would be nice.
– Kusalananda
Jul 29 at 7:44
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
the spawned window as input or output? or both at some point? the script file is what is read for commands executed in a script file, typically, but your
-ecould prefixENV=scriptfile shor something– mikeserv
Jul 28 at 8:01
I forgot, yes, both. The scriptfile should launch a new terminal window with specific geometry (--geometry) and should be fully interactive. The original scriptfile should only provide the commands to be exceuted, but in- and output should be completely via the spawned terminal window.
– t3ngu
Jul 28 at 8:14
huh? the scriptfile should... provide commands... but [i/o] ... completely via spawned terminal... thats where you lose me. is the new terminal window accepting commands from scriptfile and live input? round-robin then? or do you want to script the launch of an interactive program
&waitfor itsreturn$? until... doing more stuff?– mikeserv
Jul 28 at 8:23
Make the script check for an argument first. If there's no argument, launch a terminal to run the same script (itself) but WITH an argument, and then exit. If there is an argument, skip launching a terminal and run the other commands.
– Thomas Zwaagstra
Jul 28 at 8:41
It's unclear if you want to write a script that starts a terminal with an interactive shell ("fully interactive"), or whether you want to execute a single non-interactive command, script or part of a script in the terminal. An example of what you are trying to do would be nice.
– Kusalananda
Jul 29 at 7:44