Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <42B76D2B.CE853207@dessent.net> Date: Mon, 20 Jun 2005 18:28:11 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: lynx getting segv when following a link with right arrow key References: <20050621011321 DOT GA3060 AT efn DOT org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Report: -5.9/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.0 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Yitzchak Scott-Thoennes wrote: > On the 20050615 snapshot (and maybe other releases, haven't used lynx > in a while) lynx is repeatably segfaulting when I use the right arrow > key to follow a link. I noticed that the other day actually. The link in question was one that did not have a protocol in the URI, for example: .... I believe that this is permitted by the standards, and it allows for having a site accessible with the same links over both http: and https: at the same time. (The browser is supposed to use whichever protocol is in effect currently when presented with such a URL.) I did not take the time to figure out why lynx was segfaulting, I just switched to the linux box where lynx worked correctly on such URIs. By any chance was the link you visited the same type? It could very well be an upstream bug -- does a lynx upstream still even exist? I seem to recall reading that development on it stopped long ago. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/