xfpager, and general observations

[Dmitry DELTA Malykhanov]

Just add it after the line 878 (see below)

On Sun, 18 Aug 2002, Harry Putnam wrote:
> > Harry, could you please add one more line to the code, dumping incoming
> > commands to the file (just next to the existing fprintf statement):
> >
> > fprintf(log, "MyName = %s\n", MyName);
>
> Not sure what you wnat here.  Existing code looks like this:
>  (beginning line 871
> 871 while (tline != NULL)
> 872   {
> 873     int g_x, g_y, flags;
> 874     unsigned width, height;
> 875
> 876 	 FILE *log;
> 877	 if( (log=fopen("/home/reader/XFPAGER.LOG", "a+"))!=NULL ) {
> 878				  fprintf(log, "%s", tline);
                                  fprintf(log, "MyName = %s\n", MyName);
> 879				    fclose(log);
> 880	  }
>
> Where does the new line go?  And what does it actually do?

This line will show us what the xfpager "thinks" about it's own name. When
xfpager is reading the configuration, it's looking for strings starting
from *${MyName}.PARAMETER (where MyName is something derived from the
argv[0], actually, a sort of basename() equivalent). If the name used by
the xfpager internally is not "xfpager" for same reason, it will be unable
to process it's own configuration. For example, in my case (after moving
xfpager to xfpager.bin), the pager was looking for string
"*xfpager.bin.geometry", not "*xfpager.geometry".

--
It's me -- Delta at SDF Public Access UNIX System - http://sdf.lonestar.org

"I don't advise it, citizen, mn-e-eh... I don't advise it. You'll be eaten."