Hi, I just recognized the warning because I still use --comand in a script. I saw that instead of --command one should just use -- in future followed by the command and it's arguments, but this would not allow to pass other options to mater-terminal after the first command, which I currently do in my script, because I want to start mate-terminal with several tabs on startup of my mate desktop, and more than one of those tabs run a command, which after the removal of the --command option is not possible anymore.
So my question is, can I still do something like this after the --comand option is removed?
gnome-terminal \
--tab --command 'bash --rcfile ~/scripts/.mybash.rc' \
--tab --working-directory /scratch/ --command 'bash -c "echo \"# ~/wasf 3 /scratch/ ; pm-suspend\" ;sudo -s"' \
--tab --working-directory /scratch/tv/ \
--tab --working-directory /scratch/dl/ \
--tab --working-directory ~/develop \
--tab --working-directory ~/develop/selenium/xxx/ --command 'bash -c "~/develop/selenium/xxx/start_testloop.sh"' \
--tab
Hi, I just recognized the warning because I still use --comand in a script. I saw that instead of --command one should just use -- in future followed by the command and it's arguments, but this would not allow to pass other options to mater-terminal after the first command, which I currently do in my script, because I want to start mate-terminal with several tabs on startup of my mate desktop, and more than one of those tabs run a command, which after the removal of the --command option is not possible anymore.
So my question is, can I still do something like this after the --comand option is removed?