From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: melpa website and eww
Date: Sun, 23 Feb 2020 17:08:43 +0000 [thread overview]
Message-ID: <87lfotxmck.fsf@ucl.ac.uk> (raw)
In-Reply-To: alpine.NEB.2.21.2002211223520.27@panix1.panix.com
On Friday, 21 Feb 2020 at 12:24, Jude DaShiell wrote:
> Have you got:
> (setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3")
> in your .emacs file?
> If not, maybe try adding that and see if eww can read the site.
Thank you for the suggestion. However, the problem is not that I cannot
access/read the site but that the site uses Javascript to generate much
(all in some cases) of what it displays. eww does not support
Javascript.
--
Eric S Fraga via Emacs 28.0.50 & org 9.3.6 on Debian bullseye/sid
next prev parent reply other threads:[~2020-02-23 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 16:38 melpa website and eww Eric S Fraga
2020-02-20 17:00 ` Amin Bandali
2020-02-20 17:14 ` Eric S Fraga
2020-02-20 23:26 ` Jean-Christophe Helary
2020-02-21 17:24 ` Jude DaShiell
2020-02-23 17:08 ` Eric S Fraga [this message]
2020-02-23 18:11 ` Jude DaShiell
2020-02-24 6:33 ` Eric S Fraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfotxmck.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).