You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The initial implementation of iTerms always waits for the response from z/OS.
Describe the solution you'd like
Ideally, users are able to run a command and specify whether or not they want to wait for the output 😋
And if they decide not to wait, users should be able to specify if they want to get delayed responses OR just forget about the output of the executed command. 😋
One option could be to make users prefix the command with special command modifiers:
Prefix with :async for delayed responses
Prefix with :forget if the user is not interested in the output of the command
Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.
zFernand0
changed the title
iTerm(special): Handle asynchronous operations (delayed response | submit & forget)
iTerm(special): Handle asynchronous operations
Oct 10, 2024
Is your feature request related to a problem? Please describe.
The initial implementation of iTerms always waits for the response from z/OS.
Describe the solution you'd like
Ideally, users are able to run a command and specify whether or not they want to wait for the output 😋
And if they decide not to wait, users should be able to specify if they want to get delayed responses OR just forget about the output of the executed command. 😋
One option could be to make users prefix the command with special command modifiers:
:async
for delayed responses:forget
if the user is not interested in the output of the commandDescribe alternatives you've considered
3270 😅
Additional context
Related:
The text was updated successfully, but these errors were encountered: