ken wrote: > >another example: the notion that there's just one answer to "how > >should i display <foo>?" is a little naive. i'm sure we all might use > >any of several apps to view a specific type of content. i have a > >monolithic script that helps me deal with attachments (or inlines ;-). > >when it sees application/pdf, it asks me whether it should use xpdf, > >okular, or acroread, and arranges for an MHSHOW variable that will do > >the right thing. for msword it similarly gives me a choice between > >antiword or libreoffice. i'll bet all that prompting could be done > >using individual wrapper scripts invoked from > >mhshow-show-application/<foo> entries. > > I know what you mean ... it seems like we need a new tool. mhshow really > seems to be more about "display this content", mhstore is more about "store > this content". We don't really have something that's in the middle: > "direct this content to stdout". I know it's possible to cobble something
i don't quite follow the usage case you're picturing. at least, i don't see how it would help with the problem i described above. mhshow takes care of creating a file containing the content with a unique name -- that has value. paul =---------------------- paul fox, [email protected] (arlington, ma, where it's 60.8 degrees) _______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
