-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Juergen Weigert wrote: > On Aug 08, 08 18:52:53 -0700, Micah Cowan wrote: >> For consistency, one could also consider having screen swallow up >> mouse-tracking responses, and reissue them down only the ttys on which >> requests had been seen. >> >> But that wouldn't be a general solution, since other term-specific >> query/responses couldn't be caught by Screen, and so would always end up >> at the filter end in any case. So, perhaps I should simply apply your >> patch to obtain a general _and_ consistent solution (if a potentially >> existing-filters-breaking one), and have done with it. >> >> ...which is why this is a discussion, and not a rant. Feedback, anyone? :) > > When I originally implemented filters, the concept was, that everything > should pass through the filter process. > > A filter that relies on some data bypassing the filter, is a bad filter and > should be fixed, IMO. > > Filter syntax and semantics are horribly complex, and possibly got quite > broken over time. I haven't used any recently.
Well, that's certainly reason enough to fix it, then. :) Thanks for clarifying, Juergen. It may also be that this was never working properly; I expect that not many filters issue terminal queries, so who would have noticed? - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. GNU Maintainer: wget, screen, teseq http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIoJLI7M8hyUobTrERAmeYAJ45YAbtZQGo8nq1tWjaiQ95uBkZUgCfSgrf cvdjzZLeyTqn9avyg+p8ajc= =fVg4 -----END PGP SIGNATURE----- _______________________________________________ screen-users mailing list screen-users@gnu.org http://lists.gnu.org/mailman/listinfo/screen-users
