From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Just edbrowse
Date: Sun, 03 Jan 2016 10:52:10 -0500 [thread overview]
Message-ID: <20160003105210.eklhad@comcast.net> (raw)
In-Reply-To: <20160103104855.GI12402@122oven.adamthompson.me.uk>
It is done.
Pull, build, edbrowse jsrt, browse, ps -u
Note the arguments on the two instances of edbrowse.
Adam this is your --mode idea which I like.
makefiles and CMakeLists are adjusted.
Geoff you might want to build / run on windows to check my work.
I got rid of the path mangling software that we needed before.
Looking ahead, perhaps --mode curl sets whichproc = 'c' and runs curl_main().
Karl Dahlke
next prev parent reply other threads:[~2016-01-03 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 16:09 Karl Dahlke
2016-01-02 20:17 ` Geoff McLane
2016-01-03 10:48 ` Adam Thompson
2016-01-03 15:52 ` Karl Dahlke [this message]
2016-01-03 17:56 ` Geoff McLane
2016-01-03 19:12 ` Karl Dahlke
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=20160003105210.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).