Valentin Nechayev | 27 Jul 07:21 2016

[bug, minor] page navigation too short string

to navigate to a known page number, one should press "0" "<number>p".
At 32-bit systems, this doesn't allow entering more than 4 characters,
so, "999p" is allowed, but "1000p" is not, if refuses additional
characters after "1000".

In LYGetFile.c, this is in the row

    if (LYgetBString(&temp, FALSE, sizeof(temp), NORECALL) < 0 ||

where sizeof(temp) seems result of usage misconception because
LYgetBString() wants here a maximal input line size.

Just for me I've trivially fixed this with a magic constant:

--- src/LYGetFile.c
+++ src/LYGetFile.c
 <at>  <at>  -1141,7 +1141,7  <at>  <at> 
      * Get the number, possibly with a letter suffix, from the user.
-    if (LYgetBString(&temp, FALSE, sizeof(temp), NORECALL) < 0 ||
+    if (LYgetBString(&temp, FALSE, 11, NORECALL) < 0 ||
 	isBEmpty(temp)) {
 	return (DO_NOTHING);

(11 is maximal length of unsigned int in text, plus "p")
but one could have more advanced idea.

(Continue reading)

Jude DaShiell | 14 Jul 18:41 2016

local issuer certificate errors

Whenever I use lynx to connect to https:// type pages or get redirected to 
https:// pages I get can't get local issuer certificate continue y/n? 
All of this happens on a newly installed talkingarchlinux system.  Am I 
missing a package or do I need to configure something?


Lynx-dev mailing list
Lynx-dev <at>

Karen Lewellen | 14 Jul 17:16 2016

lynx trace file revisited?

Hi folks,
I do not need to do this often, but when I do  it is usually important.
Documenting an html code error but cannot find the lynx trace file I am 
sure was created.
As I recall the file name has some sort of special character associated.
What should the  file be called.
Additionally, is there a way to specify the name of the trace file 
created, in case one needs to do more than one?

Lynx-dev mailing list
Lynx-dev <at>

iohann | 7 Jul 21:23 2016

Re: Lynx-dev Digest, Vol 148, Issue 1

ok. thanks. reached out to askubuntu today.

only response received is: "have a closer look at documentation" ... 
which i'm doing.

again, thanks for your response.


On 07/07/2016 11:00 AM, lynx-dev-request <at> wrote:
> Send Lynx-dev mailing list submissions to
> 	lynx-dev <at>
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> 	lynx-dev-request <at>
> You can reach the person managing the list at
> 	lynx-dev-owner <at>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Lynx-dev digest..."
> Today's Topics:
>     1. ssl - compile - https (zoho)
>     2. ssl - compile - https (zoho)
>     3. ssl - compile - https (zoho)
(Continue reading)

zoho | 6 Jul 22:13 2016

ssl - compile - https

cannot get compiled lynx to work with https.

./configure --with-ssl
sudo make install

seems to go well. no error messages.
lynx installs at /usr/local/bin/lynx

yet, starting /usr/local/bin/lynx, then attempting to access https site 
fails with message: this client does not contain support for HTTPS URLs

i am running ubuntu 16.04.

"sudo apt-get install lynx"
works smoothly, installs at /usr/bin/lynx and permits access to HTTPS.

any suggestions?

thanks in advance for help.


Lynx-dev mailing list
Lynx-dev <at>

Francesco Ariis | 21 Jun 00:18 2016

SSLcerts config help

Hello lynx users,
    I am trying to configure lynx to handle ssl certs following
`README.sslcerts` [1]. I am using Lynx Version 2.8.9dev.1 (12 Mar 2014)
on Debian stable.
I am having problems with setting SSL_CERT_DIR and SSL_CERT_FILE
environment variables.


Long story short, the guide asks you to determine where `libcrypto.a` is,
so I invoked:

    u <at> m:/usr$ find -name libcrypto.a

Then, to determine the default location for the certs the
guide asks you to run:

    strings libcrypto.a  | grep -in cert | less

I modified my .bashrc to export those variables:

    u <at> m:~$ echo $SSL_CERT_DIR; echo $SSL_CERT_FILE
(Continue reading)

kaltheat | 10 May 19:39 2016

Extend gopher client functionality to support URL scheme


recently I realized that lynx' gopher client implementation does not cover the (non-RFC) URL
scheme[1,2]. This scheme is supported by Overbite Addon for Firefox for instance and gives a smoother
experience when surfing from gopher oceans into http seas. You can test it using this[3] address. With
lynx you'll see an information page generated by the gopher server once the client does not handle the URL
scheme properly, with Overbite there is a seamless transition.

Would you mind to extend lynx' gopher client?


[2] gopher://
[3] gopher://

Lynx-dev mailing list
Lynx-dev <at>

Shérab | 5 May 18:23 2016

Some links not recognized on

Dear all,

I use lynx to read

This used to work quite well but does not work so well any longer.

More precisely, e.g. in the notification area, no links are shown to see
the object one received a notification for anylonger. This worked

I had a quick look to the HTML source and from that I got the feeling
that the links are still there, so it looks as if for some reason they
are not properly recognized.

Can somebody else reproduce problem?

Is there a known fix?

Is it FB's HTML that is not valid or lynx that has a bug?

Thanks a lot for any help!


Lynx-dev mailing list
Lynx-dev <at>
Thomas Dickey | 30 Apr 02:00 2016

Re: ANN: lynx2.8.9dev.9

----- Original Message -----
| From: "Axel Beckert" <abe <at>>
| To: lynx-dev <at>
| Cc: 822958-forwarded <at>
| Sent: Friday, April 29, 2016 7:12:27 AM
| Subject: Re: [Lynx-dev] ANN: lynx2.8.9dev.9
| Hi Thomas,
| On Wed, Apr 27, 2016 at 01:12:32AM +0000, Thomas Dickey wrote:
| > * restore fix to filter out left-to-right marks which was broken in
| >   refactoring in 2.8.9dev.2, and also filter out right-to-left
| >   marks
| >   (Debian #808949) -TD
| Thanks for taking care of bugs reported in Debian!
| Nevertheless, in this case, the fix might have broken something else
| as it probably caused the following regression reported in Debian
| today:

yes/no: the report noted breakage in an earlier fix to remove the feature:

    ignore LEFT-TO-RIGHT-MARK (U+200E) in HTML files (Debian #408835) -TD

If someone sees it "working" in some version, that is accidental (i.e., a bug), since
neither ncurses nor slang actually support bidi in the sense that they know
what's on the screen between the (zero-width!) markers.

(Continue reading)

Vincent Lefevre | 29 Apr 16:29 2016

Re: ANN: lynx2.8.9dev.9

On 2016-04-29 13:12:27 +0200, Axel Beckert wrote:
> I can't reproduce the regression in an uxterm since it always seems to
> show the exclamation mark at the end, independent of the lynx version.

AFAIK, uxterm, like most terminals, don't have bidi support.

> (mlterm shows the exclamation mark indeed at different places, but
> only shows boxes instead of hebrew characters for me.)

To see the Hebrew characters, you may need to disable Xft in the
font config. I got them with:


which is chosen by default once Xft is disabled (but then, the
behavior may also depend on packages that are installed).


Vincent Lefèvre <vincent <at>> - Web: <>
100% accessible validated (X)HTML - Blog: <>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Lynx-dev mailing list
Lynx-dev <at>

Thomas Dickey | 27 Apr 03:12 2016

ANN: lynx2.8.9dev.9


2016-04-26 (2.8.9dev.9)
* add workaround for servers such as which fail to close
  the connection when they finish sending compressed data.  This relies on
  the content-length (report by Klaus-Peter Wegge) -TD
* restore fix to filter out left-to-right marks which was broken in refactoring
  in 2.8.9dev.2, and also filter out right-to-left marks (Debian #808949) -TD
* fix build for current gnutls configuration which dropped the
  gnutls_protocol_set_priority function (reported by Axel Beckert, Andreas
  Metzler) -TD
* modify CF_LD_RPATH_OPT configure macro, changing FreeBSD case to use
  -Wl,-rpath rather than -rpath option.  According to FreeBSD #178732, either
  works since FreeBSD 4.x; however scons does not accept anything except the
  -Wl,-rpath form -TD
* add null-pointer checks for ssl_ctx in HTTP.c in case of error from calls
  on SSL_CTX_new (report by Yuan Jochen Kang) -TD
* update config.guess (2016-01-01), config.sub (2016-01-01)
* update da.po, fi.po, tr.po from


(Continue reading)