> If the PRINTER isn't in the printcap file, and you try to print
> (I'm using "follow tcp stream"), we get a SIGPIPE and
> it aborts. (I initially had an empty printcap file, I used lprng)
We should probably catch the SIGPIPE. You'll still not get any
printout, obviously....
> I like the way the "follow tcp stream" colorizes input,
> but how do I get this out to the printer (or generate a postscript
> file).
We don't support PostScript printing in "follow TCP stream". If
somebody wants it, I'll look at implementing it, *but* will not look at
doing anything more sophisticated than "wrap lines at 80 characters" -
you'll have to get somebody who knows how to get PostScript code to do
line-wrapping at the paper width if you want more - *and* won't look at
doing color PostScript (again, get somebody who knows PostScript if you
want that). (If somebody says "do it this way", I'll look at doing
that, *but* will refer any bugs to that somebody....)
> I have (in preferences/printing):
> format: postscript
> print to: file
> but I just see an ascii dump (not a postscript image of the colorized window).
As per the previous paragraph, we don't support PostScript printing in
"follow TCP stream" - if it gets implemented, the preferences option
will control it.
> I also can't follow one side of the conversation (I set a filter
> expression [which did what I want], but then when I said "follow tcp
> conversation I get both sides).
Well, yes, conversations are generally considered to be two-sided; an
option could, I guess, be added to follow one side.