Brian, I appreciate your maintainership of run-mailcap, but first you take a long time to reply then you upload immediately without waiting for feedback on your comments. You have a couple people here interested in testing and providing feedback prior to release...
Brian White wrote: [Thu Dec 03 2009, 03:14:32PM EST] > > I thought "copiousoutput" meant "non-interactive stdout". Am > > I mistaken? > > "copiousoutput" indicates that the program produces a lot of output > and should be fed into a "pager" program so as to not overwhelm the > user. I've added a "--nopager" option in the latest upload. So by strict RFC interpretation, a mailcap rule specifying "copiousoutput" implies non-interactive output on stdout, however a mailcap rule lacking "copiousoutput" does not strictly imply the opposite. Unfortunately this strict interpretation of the flag isn't useful for a couple reasons: 1. there's no way for the mailcap rule to know the length of the output since it depends on the input. 2. the use of a pager depends on the size of the output compared to the size of the terminal, but the mailcap doesn't know the size of the terminal either. This is probably why mutt deviates from strict RFC for the "copiousoutput" flag, meaning that mutt uses the flag to find rules that generate non-interactive stdout. > > Unfortunately I know of at least one filter (unoconv) that > > connects to the X server (to access the openoffice server, > > I believe). So if we want that to work, it's not really an option > > to unset DISPLAY prior to running mailcap tests. > > I've left "cat" in place though it now unsets DISPLAY. There's no > perfect solution, I'm afraid. Thanks for trying to provide a solution. I understand the reasons for your choices, but unfortunately the various changes you've made fail to provide a method of achieving the result I want (which depends on "copiousoutput") so I'll have to continue to maintain my fork. Aron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
