Return to Answer

Good questions are based on research on the subject of the question. Once that is done, you have at least a clear assumption on the options you have, and you can ask specific question(s) to achieve your goal and exactly find out were your assumptions may be incorrect. Your question then is based on clear information, either correct or not, and an answer can be given accordingly.

You are doing it exactly the opposite way. You start with a vague idea of what you think you want to achieve. However, since you have not put any effort in what are technically the options (at least that's how it seems), you are not able to draw a clear picture at all.

As a result, and I think that is the worst, you are asking us to join you in your attempt to create weird solutions (just come to the idea of opening a file without open() or with open() in python), based on obviously incorrect assumptions.
While doing so, you ignore new information people offer you, and you stick to your own incorrect assumptions, constantly give us contradictory information, [like here][1], in the question: "I don't want a script", in a comment: "a script doesn't matter".

Finally, reposting the question "so other users will notice", completes the impression of a messy way of asking questions [1]: How to make a command execute once a certain command terminates?

Good questions are based on research on the subject of the question. Once that is done, you have at least a clear assumption on the options you have, and you can ask specific question(s) to achieve your goal and exactly find out were your assumptions may be incorrect. Your question then is based on clear information, either correct or not, and an answer can be given accordingly.

You are doing it exactly the opposite way. You start with a vague idea of what you think you want to achieve. However, since you have not put any effort in what are technically the options (at least that's how it seems), you are not able to draw a clear picture at all.

As a result, and I think that is the worst, you are asking us to join you in your attempt to create weird solutions (just come to the idea of opening a file without open() or with open() in python), based on obviously incorrect assumptions.
While doing so, you ignore new information people offer you, and you stick to your own incorrect assumptions, constantly give us contradictory information, like here, in the question: "I don't want a script", in a comment: "a script doesn't matter".

Finally, reposting the question "so other users will notice", completes the impression of a messy way of asking questions

Good questions are based on research on the subject of the question. Once that is done, you have at least a clear assumption on the options you have, and you can ask specific question(s) to achieve your goal and exactly find out were your assumptions may be incorrect. Your question then is based on clear information, either correct or not, and an answer can be given accordingly.

You are doing it exactly the opposite way. You start with a vague idea of what you think you want to achieve. However, since you have not put any effort in what are technically the options (at least that's how it seems), you are not able to draw a clear picture at all.

As a result, and I think that is the worst, you are asking us to join you in your attempt to create weird solutions (just come to the idea of opening a file without open() or with open() in python), based on obviously incorrect assumptions.
While doing so, you ignore new information people offer you, and you stick to your own incorrect assumptions, constantly give us contradictory information, [like here][1], in the question: "I don't want a script", in a comment: "a script doesn't matter".

Finally, reposting the question "so other users will notice", completes the impression of a messy way of asking questions [1]: How to make a command execute once a certain command terminates?

Good questions are based on research on the subject of the question. Once that is done, you have at least a clear assumption on the options you have, and you can ask specific question(s) to achieve your goal and exactly find out were your assumptions may be incorrect. Your question then is based on clear information, either correct or not, and an answer can be given accordingly.

You are doing it exactly the opposite way. You start with a vague idea of what you think you want to achieve. However, since you have not put any effort in what are technically the options (at least that's how it seems), you are not able to draw a clear picture at all.

As a result, and I think that is the worst, you are asking us to join you in your attempt to create weird solutions (just come to the idea of opening a file without open() or with open() in python), based on obviously incorrect assumptions.
While doing so, you ignore new information people offer you, and you stick to your own incorrect assumptions, constantly give us contradictory information, [like here][1], in the question: "I don't want a script", in a comment: "a script doesn't matter".

Finally, reposting the question "so other users will notice", completes the impression of a messy way of asking questions [1]: How to make a command execute once a certain command terminates?

Good questions are based on research on the subject of the question. Once that is done, you have at least a clear assumption on the options you have, and you can ask for the way to achieve your goal and where your assumptions may be incorrect. Your question then is based on clear information, either correct or not, and an answer can be given accordingly.

You are doing it exactly the opposite way. You start with a vague idea of what you think you want to achieve. However, since you have not put any effort in what are technically the options, you are not able to draw a clear picture.

As a result, you are asking us to join you in your attempt to create weird solutions, based on a lack of basic knowledge. While doing do, you ignore valuable information people offer you, you stick to your own incorrect assumptions, constantly give us contradictionary information, [like here][1], in the question: "I don't want a script", in a comment: "a script doesn' matter" and so on.

Finally, repeating the question "so other users will notice", and "reposted my question", "may seem like a duplicate"?? completes the mess. [1]: How to make a command execute once a certain command terminates?

Good questions are based on research on the subject of the question. Once that is done, you have at least a clear assumption on the options you have, and you can ask specific question(s) to achieve your goal and exactly find out were your assumptions may be incorrect. Your question then is based on clear information, either correct or not, and an answer can be given accordingly.

You are doing it exactly the opposite way. You start with a vague idea of what you think you want to achieve. However, since you have not put any effort in what are technically the options (at least that's how it seems), you are not able to draw a clear picture at all.

As a result, and I think that is the worst, you are asking us to join you in your attempt to create weird solutions (just come to the idea of opening a file without open() or with open() in python), based on obviously incorrect assumptions.
While doing so, you ignore new information people offer you, and you stick to your own incorrect assumptions, constantly give us contradictory information, [like here][1], in the question: "I don't want a script", in a comment: "a script doesn't matter".

Finally, reposting the question "so other users will notice", completes the impression of a messy way of asking questions [1]: How to make a command execute once a certain command terminates?