How to run several bash commands put in bash command line without needing and requiring a script file.

Because I'm actually a windows guy and new here so for illustration is sort of :

bash "echo ${PATH} & echo have a nice day!"

will do output, for example:

/usr/local/bin:/usr/bin:/bin:/opt/bin:
have a nice day!

as it is analogous to windows:
cmd /c "echo %path% & echo have a nice day!"

Sincere help is really grateful to my thankfulness..

It depends on what you want as output, and whether you want the second part to depend on the first.

To get the output based on your example, something like one of these would work...

The && is a conditional and operator, often called a short-circuit operator, and means that if the part on the left succeeds then do the part on the right, so execution of the second is conditional, it depends on the success of the first (see below).

The ; denotes the end of a command and allows you to put multiple commands on a single line, without dependence on each other.

Conditional expressions are more useful for constructs other than simply echoing output (which presumably always succeeds). You might try something like this:

If the math condition in ((..)) is true, then the string will be echoed, otherwise not.

I might as well confuse the issue with expect and autoexpect.

If they are sequential commands, you can use "&" and "&&." If you use "&&" the system will wait for the first command to finish before starting the second one. Here's an example I use frequently:

Will execute echo $PATH in the background and echo have a ... immediately in the foreground. Which isn't what you want

You can use semi-colon as separator like "pwd;ls;cd /tmp"

But I high recommend placing them inside script file. Bash script is mostly collection of Linux commands.

not to speak about -c:

1 members found this post helpful.

This thread demonstrates how a simple question with somewhat vague parameters will be seen differently by each person who reads it.

It would be helpful to us and to themselves if the OP would return and clarify exactly what they are trying to accomplish, with their actual use case. Similarity to a window$ use case is not a sufficient requirements list!

1 members found this post helpful.