Stepping back slightly, I think there's a wider issue here. Currently various desktop applications are hooked to use notify-osd, browser, chat programs, power-management.
The logical extension is to argument command-line programs to push information to notify; however I doubt those those small command line tools will really want to link and depend on libnotify instructure; so perhaps there's a case for doing this like 'bash_completion'; refer to a directory and then ship program-specific shell scripts that hook into the infrastructure---where the central infrastructure is doing things like detecting that the shell in question is in the background and not- focused. We shouldn't be printing numeric exit codes for the applications, but application-specific extensions could decode those into human-readable text (the man code normally documents what is what) or at a minimum "Finished sucessfully"/"Experienced a problem" perhaps. Somebody explicitly mentioned that this should also work with commands being run across ssh sessions. The top application to start with for me with be 'wget'; probably followed by 'scp'. The other option is to hook gnome-terminal et al through the ASCII escape code terminal infrastructure (currently used to update the titlebar with "u...@machinename"). -- [PATCH] Add desktop notification of completed commands https://bugs.launchpad.net/bugs/315932 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
