From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] edbrowse and edbrowse-js not communicating
Date: Mon, 14 Dec 2015 13:12:01 -0500 [thread overview]
Message-ID: <20151114131201.eklhad@comcast.net> (raw)
In-Reply-To: <87wpsgnbzg.fsf@mushroom.localdomain>
I fear there will be a lot of confusion in this regard
for quite some time, and I wonder,
is it possible to have edbrowse check at run time
whether it has the correct and latest tidy, and issue a warning message if it does not?
We did this with curl for a time,
when we just had to have the latest or edbrowse wouldn't run.
See main.c line 1042.
I don't think there is anything quite this convenient for tidy though.
Karl Dahlke
next prev parent reply other threads:[~2015-12-14 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 15:32 Chuck Hallenbeck
2015-12-14 18:04 ` Chris Brannon
2015-12-14 18:12 ` Karl Dahlke [this message]
2015-12-15 4:55 ` Chris Brannon
2015-12-15 12:58 ` Adam Thompson
2015-12-17 10:44 ` Chris Brannon
2015-12-19 12:37 ` Adam Thompson
2015-12-19 12:58 ` Chris Brannon
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=20151114131201.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).