I'm answering you in private, because I don't want to generate more noise in the list. I have some problems reading your mail (I think we have some understanding problem, maybe my english is not good enough).
> Take this guy's plumber conf: > he's got about 7 rules in there. > > $ grep -e menu -e run ~/src/req/src/port.*.awk | wc > 259 1658 19622 > > That's a little different, isn't it? Those really are 259 actions, each > set up in about two lines. Because of that number it comes with a > menu. I don't understand what do you want to show with this comparision. Do you want ship your app with all these default rules? > With req you can further match on context. E.g.: Given a word in the > cut buffer, it'll read the currently focused x11 window's wm_name > (possibly classify it as a file by trying to obtain it's mimetype), and > send you to the documentation for your currently focused document's > language. It's sound good... > And classification is also quite handy. It'll construct a namespace > with the matching regex' results named. Simplifies the rules a lot! .. but maybe is too much complex. I think that almost of the cases doesn't need these complex features, so they can be removed and it will make it more simple. > All this to make it reasonable to follow the itch: Hey, i just did that > twice, pasting something into the very same command. Let's set up a > rule, it'll barely take me longer than doing that again. I don't understand you here. > ...sorry, i got carried away again. You never feel caged in your > plumber setup? What am i missing? I'm sorry, but I don't understand your question or where you are missed. -- Roberto E. Vargas Caballero
