Interesting, this is happening with bash and so far lynx is the only program doing this. Bash did have a recent update and has quite the bug colony some of them old enough to be called features. The timer internal in bash is probably still not working after all of these years.

On Sun, 15 Apr 2018, David Woolley wrote:

Date: Sun, 15 Apr 2018 08:54:33
From: David Woolley <for...@david-woolley.me.uk>
To: lynx-dev@nongnu.org
Subject: Re: [Lynx-dev] lynx startup message

On 15/04/18 13:44, Jude DaShiell wrote:
 I can also check slint and debian to find out if this is specific to
 archlinux and if so, probably the archlinux packages were built
 incorrectly.

If it was built for the wrong architecture, it could cause problems, as the low level code will try and run it with /bin/sh if it doesn't start with a known prefix. All recognized binary formats have unique prefixes, and a prefix of "#!" indicates that a named interpreter, rather than the shell, is to be run.

_______________________________________________
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


--


_______________________________________________
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev

Reply via email to