edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] css on demand
Date: Fri, 16 Feb 2018 11:59:01 -0500	[thread overview]
Message-ID: <20180116115901.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1802141441260.13728@debian.pulsar.com>

> many links are not displayed, only their surrounding braces are present.

I finally fixed this one. Trying to clean things up for a new version.
Also amazon comes up for me in just a few seconds with full javascript and no exclusions.

Do you still have the curl https download problem?
Would be nice to understand that one?
Did you check the versions of libcurl and libcurl-devel to make sure they're the same?

Karl Dahlke

  reply	other threads:[~2018-02-16 16:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 15:59 Karl Dahlke
2018-02-14 19:21 ` Adam Thompson
2018-02-14 19:50   ` Chuck Hallenbeck
2018-02-16 16:59     ` Karl Dahlke [this message]
2018-02-17 10:52       ` [Edbrowse-dev] URL.prototype.slice Kevin Carhart
2018-02-17 11:25         ` Karl Dahlke
2018-02-15  6:24 ` [Edbrowse-dev] css on demand Kevin Carhart
2018-02-15  8:17   ` Karl Dahlke
2018-02-15  8:34     ` Kevin Carhart

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180116115901.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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 NNTP newsgroup(s).