Grant wrote:
>> > In this instance I have two blank lines in the delivered HTML between>> > htmltag1 and htmltag2: >> > >> > <htmltag1></htmltag1> >> > [ictag][/ictag] >> > [ictag][/ictag] >> > <htmltag2></htmltag2> >> > >> > If I use the filter like this: >> > >> > <htmltag1></htmltag1>[filter no_white] >> > [ictag][/ictag] >> > [ictag][/ictag] >> > [/filter]<htmltag2></htmltag2> >> > >> > I get only one blank line, so it is an improvement. Should it be >> > possible to remove the blank lines entirely? >> snip >> >> I may be crazy, but I see two lines with "[ictag][/ictag]" on them >> between "<htmltag1></htmltag1>" and "<htmltag2></htmltag2>". When >> most people on this list say "blank lines" we mean either a line with >> no characters other than the line-terminator (\n) or a line with >> whitespaces (tabs and spaces) followed by the line-terminator. > > I'm sorry, I should have explained myself better. The interchange > tags (ictags) are parsed before the HTML is delivered. When they are > parsed, a bunch of blank lines are left where they had been. BUT! > The apache list pointed out to me that the Interchange::Link module I > am using as the link between interchange and apache is delivering the > content like this: > > while( <SOCK> ) { > push @out, $_; > } > > and I should be able to filter the blank lines most efficiently that > way. This is an alternative to the [filter][/filter] method I had > been working on. Can anyone show me how to regexp the blank lines out > considering the above code?while( <SOCK> ) { push @out, $_ if /\S/; }Hi Rob, Is that better than: push @out, $_ unless /^\s*$/;
I think it's simply more readable. Rob -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
