这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@Archenoth
Copy link
Contributor

I've added an optional final argument to the BackgroundJob constructor for a PendingIntent that it will respond to with the results of the commands that it has run. (A "result" bundle containing stdout, stderr, and the process exit status)

I've also added a "pendingIntent" extra that will be pulled from service_execute requests that can hold these new PendingIntents, so Termux can respond to things that can invoke these intents with the resulting command's output.

The immediate practicality of this is that it will allow things like this issue in termux-tasker to be solved.

This commit adds an optional final argument to the BackgroundJob
constructor for a PendingIntent to return the results of its
execution to, and also attempts to pass an optional pendingIntent to
it from the Service start intent
@Archenoth Archenoth force-pushed the BackgroundTaskResponses branch from 9bbd1d4 to f16e579 Compare December 2, 2019 18:48
@Archenoth
Copy link
Contributor Author

(The push was rebasing this onto master's new commits)

@fornwall fornwall merged commit 7f7c1ef into termux:master Jan 5, 2020
@fornwall
Copy link
Member

fornwall commented Jan 5, 2020

@Archenoth Thanks a lot! This change will be part of version 0.86 of the Termux app, which will be released within a day.

You're welcome to join https://gitter.im/termux/dev to discuss development (and ping me if I'm slow to merge any PR)!

@Archenoth Archenoth deleted the BackgroundTaskResponses branch January 5, 2020 01:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants