Re: LYNX-DEV To ac developers: please answer something

[David Combs]

Obviously, the PROGRAM should fill in the information!

the machine being used, the os, terminal type (at least
what the computer THINKS it is), the current url (with
question "is this most resently gotten/tried url the
one you have the problem with?".

Also, "include the (printed) page?".
Also, "include the HTLM for the page?".

That way it would be FAR EASIER for someone to
email via form to lynx-dev -- and thus
they should likely actually DO it that way!

> From address@hidden Fri Dec 12 04:03:26 1997
> Date: Fri, 12 Dec 1997 06:22:22 -0500
> From: address@hidden (Larry W. Virden, x2487)
> Subject: Re: LYNX-DEV To ac developers: please answer something
> In-Reply-To: <address@hidden> of Fri, 12 Dec 1997 07:45:02 +0300 (MSK)
> To: address@hidden
> Sender: address@hidden
> Precedence: bulk
> Reply-To: address@hidden
> 
> your note arrived at the mailing list.
> 
> Please understand - unless you provide a full description of the machine
> being used, the os being used, the terminal type being used, the url being
> used, and the actions taken, many folk won't have the time to try to track
> down this information from previous postings so that they can figure out
> where the problem might be.
> 
> Developers, we have talked in the past about creating a bug report form
> that folk could be encouraged to use - perhaps even a form 
> distributed with lynx that would mail the report to us - which details
> the hardware, software, version of lynx, compile options, url of
> the problem, etc.
> 
> Anyone who is looking for a way to contribute to lynx want to build
> such a thing for this next release?
> 
> -- 
> Larry W. Virden                 INET: address@hidden
> <URL:http://www.teraform.com/%7Elvirden/> <*> O- "We are all Kosh."
> Unless explicitly stated to the contrary, nothing in this posting should 
> be construed as representing my employer's opinions.
>