From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Just edbrowse
Date: Sun, 3 Jan 2016 10:48:55 +0000 [thread overview]
Message-ID: <20160103104855.GI12402@122oven.adamthompson.me.uk> (raw)
In-Reply-To: <20160002110930.eklhad@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
On Sat, Jan 02, 2016 at 11:09:30AM -0500, Karl Dahlke wrote:
> For the js engine, invoke
> edbrowse --runjs
> for the curl server, invoke
> edbrowse --runcurl
> and so on for as many variations as we wish, never having to change makefiles
> or CMakeLists.txt again.
> And we can throw away all that code around ebjs.c line 67,
> because all you have to do is run argv[0] with different arguments.
Makes sense.
> If argv[1] is one of our magic strings, set whichproc appropriately
> and run in that mode.
>
> Perhaps magic string arguments aren't your cup of tea,
> but it's far better than all the build / distribution issues, and symlinks or copies
> of renamed images in the correct bins, and so on.
> Geoff is on this list now, so feel free to chime in and tell us
> that this is definitely the way to go.
I think I'd probably have a --mode js option,
but that's because I've been thinking it'd also be nice to have a few other
options like --config <config_file> to override the default .ebrc.
Tbh though, --runjs, --runcurl etc don't bother me that much.
It certainly beats the multiple copies of the same binary option.
Cheers,
Adam.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-01-03 10:48 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 [this message]
2016-01-03 15:52 ` Karl Dahlke
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=20160103104855.GI12402@122oven.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).