On Tue, Feb 03, 2004 at 09:07:31PM -0500, Harland Christofferson wrote: > > >> > >> Tom will be able to give you the correct answer, but my GUESS > would be > > > >offhand, no - setting LINES and COLUMNS normally overrides the screensize > >of a curses-based program (slang, too), even if the corresponding > numbers > >are set in the terminfo/termcap. But that may depend on the system > - some > >terminfo entries omit lines/columns to bias the application toward > >obtaining that information in another way. > > > >(I don't see the original email here, just your reply). > > > > the gist of my original email is this: > > i run a script that calls lynx-ssl w/ the -cmd_script option in an > xterm that is COLUMNS=163 LINES=40 and pipe the stdio to a text file, > i.e., lynx -cmd_script=myscript www.someurl.com > output.txt. COLUMNS=163 > LINES=40 environment variables are set by the size of my xterm window. > i want to call this lynx session from a cron job. i need lynx to > think that the xterm (stdio) window size is at least 163x40 when > run from crontab. the default values are much smaller than what i > wish to use. is there a workaround?
It seems to work (on Debian testing using lynx 2.8.4 and current lynx - if I know what I'm looking for, I may be able to spot the problem. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
pgp00000.pgp
Description: PGP signature
