But I have to respond: Or you could grab something similar and use that as a beginning point. Say, for this application, `clipman` which gives me a popup list of the last few clipboard entries. Get into that and add some regexp filter and log output and it need not even interfere with the original functionality.
I think that both article and you are missing a very big aspect of development - ongoing support.
This is specially problematic when using existing code to create new product for a specific use case\client. It may not take very long but what everyone seems to forget is that this new product has to be maintained. Every time new feature is added to base code, it has to be tested with that new product as well. Repeat that 10-15 times and it becomes difficult if not impossible to add new feature to base code without either breaking some downstream code or getting bogged in updating numerous programs and then testing and then fixing the issues then testing again...
"The new product has to be maintained" ... If i'm the only one using it, i kindof assume that burden implicitly.
One of the great ideas in open source is that others can use my software without me having a "maintenance burden" for their use. They can maintain their own copy if they like, depend on me, or decide shit don't work.
If I did my proposed hack i doubt I'd bother the upstream developers with it; if dozens of users like it, maybe later it could be made worthy of further public consideration. But "is the maintenance burden too high" as a consideration before you begin writing is a great excuse to never try.
But I have to respond: Or you could grab something similar and use that as a beginning point. Say, for this application, `clipman` which gives me a popup list of the last few clipboard entries. Get into that and add some regexp filter and log output and it need not even interfere with the original functionality.