Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!mathcs.emory.edu!km From: km@mathcs.emory.edu (Ken Mandelberg) Newsgroups: comp.windows.open-look Subject: Re: textsw filters Message-ID: <7241@emory.mathcs.emory.edu> Date: 25 Mar 91 18:58:31 GMT References: <9918@discus.technion.ac.il> Sender: news@mathcs.emory.edu Reply-To: km@mathcs.emory.edu Organization: Emory University, Dept of Math and CS Lines: 28 In article <9918@discus.technion.ac.il>, devil@techunix.BITNET (Gil Tene) writes: |> Hello OpenPeople, |> |> There have been some requests for info on textsw filters for the |> extras menu. First, let me note that textedit(1) explians this |> quite well, except for a few typos with file names. |> |> In short, Filters are simple programs that get data in stdin and |> put it out to stdout, modifying it if needed. textsw calls filters |> giving them the current selection as input, and replacing it with |> whatever they output. |> -------------------------------------------------------------------- The problem is that there are additional restrictions on textsw filters that are not documented. By experiment, I've found that if the filter itself creates a window during its execution, the original window loses track of the selection, and never replaces the text with the filters output. This makes it impossible to write an interactive filter, -- Ken Mandelberg | km@mathcs.emory.edu PREFERRED Emory University | {rutgers,gatech}!emory!km UUCP Dept of Math and CS | km@emory.bitnet NON-DOMAIN BITNET Atlanta, GA 30322 | Phone: Voice (404) 727-7963, FAX 727-5611