OmaSettings 1.1.2

Updating a plugin used to open a terminal on top of the settings window. Now it happens in the window.

• The Update button no longer opens a terminal. The flow it ran is only interactive because it prints a diff and asks, and this page can ask better: a plugin that is behind now says how many commits are waiting and what the first three of them say, read while the update check is already talking to the remote, so it costs nothing extra.
• A row says how its update went. Upstream's own answer, kept whether it worked or not — so "cannot fast-forward; you have local changes" lands on the row instead of flashing past in a terminal that has already closed.
• The window comes back. Anything that changes a file under the plugins directory makes the shell reload every plugin widget, this window's host included, so a plugin cannot update another plugin and stay on screen. The update now survives that on its own and summons the window back to the Plugins page with the result waiting on it. The page says so up front, rather than leaving you to work out where the settings went.

Add and remove still hand off to a terminal. Both genuinely ask questions and print what they did.