lynx-dev more minore patches

[Leonid Pauzner]

* Relax warning from HTAlert to HTUserMsg on REFRESH_URL_NOT_ABSOLUTE.
* More tweaks on transfer rate calculation.



diff -u old/lycharut.c ./lycharut.c
--- old/lycharut.c      Sat Dec 12 20:10:36 1998
+++ ./lycharut.c        Thu Dec 24 20:18:54 1998
@@ -2888,7 +2888,7 @@
                     *  but this is a Netscapism, so don't
                     *  expect the author to know that. - FM
                     */
-                   HTAlert(REFRESH_URL_NOT_ABSOLUTE);
+                   HTUserMsg(REFRESH_URL_NOT_ABSOLUTE);
                    /*
                     *  Use the document's address
                     *  as the base. - FM


diff -u old/htalert.c ./htalert.c
--- old/htalert.c       Fri Dec 25 13:21:06 1998
+++ ./htalert.c Wed Dec 30 10:47:40 1998
@@ -111,8 +111,11 @@
        if (transfer_rate <= 0)    /* the very first time */
            transfer_rate = (bytes) / (now - first);   /* bytes/sec */

-       /* optimal refresh time: every 0.2 sec */
-       if ((bytes - bytes_last) > (transfer_rate / 5)) {
+       /* optimal refresh time: every 0.2 sec, use interpolation */
+           /* transfer rate is not constant when we have partial content */
+           /* in a proxy, so interpolation lie - will check every second */
+           /* at least for sure */
+       if (((bytes - bytes_last) > (transfer_rate / 5)) || (now != last)) {

            bytes_last += (transfer_rate / 5);  /* until we got next second */



diff -u old/environm.htm ./environm.htm
--- old/environm.htm    Thu Dec 24 04:27:22 1998
+++ ./environm.htm      Sat Dec 26 01:43:36 1998
@@ -7,20 +7,19 @@

 <em>ENVIRONMENT</em>
        In addition to various  "standard"  environment  variables
-       such  as HOME, PATH, USER, DISPLAY, TMPDIR, etc, Lynx utilizes
-       several Lynx-specific environment variables, <a href="#env">if they
-       exist</a>.
+       such as HOME, PATH, USER, DISPLAY, TMPDIR, etc, Lynx utilizes
+       several Lynx-specific environment variables, <a href="#env">if they 
exist</a>.

-       Others  may be created or modified by Lynx to pass data to
-       an external program, or  for  other  reasons.   These  are
+       Others may be created or modified by Lynx to pass data to
+       an external program, or for other reasons.  These are
        listed separately <a href="#setenv">below</a>.

-       See  also the sections on <a href="#cgi">SIMULATED CGI SUPPORT</a> and
+       See also the sections on <a href="#cgi">SIMULATED CGI SUPPORT</a> and
        <a href="#language">NATIVE LANGUAGE SUPPORT</a>, below.

        Note:  Not all environment variables apply to all types of
-       platforms  supported by Lynx, though most do.  Feedback on
-       platform dependencies is solicited. See also <a 
href="#dos">win32/dos</a> specific
+       platforms supported by Lynx, though most do.  Feedback on
+       platform dependencies is solicited.  See also <a 
href="#dos">win32/dos</a> specific
        variables.

 <a name="env"><em>
@@ -105,7 +104,7 @@
                            the  form  PROTOCOL_proxy  (literally:
                            http_proxy,  ftp_proxy,  gopher_proxy,
                            etc), to "http://some.server.dom:port/";.
-                           See <a href="#proxy">below</a> for details, and  
examples.
+                           See <a href="#proxy">details and examples</a>.

        WWW_access_GATEWAY
                            Lynx still  supports  use  of  gateway
@@ -117,8 +116,7 @@
                            discontinued.  Note that  you  do  not
                            include  a  terminal '/' for gateways,
                            but do for proxies specified by PROTOCOL_proxy
-                           environment variables.  See
-                           <a href="#proxy">below</a> for details.
+                           environment variables.  See <a 
href="#proxy">details</a>.

        WWW_HOME
                            This  variable,  if set, will override