From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] js progress update
Date: Wed, 8 Jan 2014 12:40:47 +0000 [thread overview]
Message-ID: <20140108124047.GB3935@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140008060551.eklhad@comcast.net>
On Wed, Jan 08, 2014 at 06:05:51AM -0500, Karl Dahlke wrote:
> > so I can check if this is an edbrowse issue or a libmozjs24d debian package issue.
>
> I would contact Jean, who contacted me in the first place.
> He wants edbrowse in debian, and discovered the problem building against moz26.
> He may know how those libraries are built and packaged etc.
> He is French, but his English is perfect!
>
> mengualjeanphi@free.fr
Thanks, will do. Whilst I do this, is there any chance people could test my
fork of edbrowse as well? The Spidermonkey 24 build process is relatively
painless, and it'd be *extremely* useful as I *think* I've squashed all the
obvious bugs, but there are probably many I've missed.
I'm now running this as my default edbrowse (so default editor and web browser)
so hopefully I'll discover various things,
but obviously the more testing the better.
Also, I've reformatted the code and pushed the commit,
so hopefully it should be ok for merging into the main code base soon.
As always, any feedback (especially code review) is very welcome.
Cheers,
Adam.
next prev parent reply other threads:[~2014-01-08 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 11:05 Karl Dahlke
2014-01-08 12:40 ` Adam Thompson [this message]
2014-01-14 20:43 ` Chris Brannon
2014-01-14 21:27 ` Adam Thompson
2014-01-14 22:17 ` Chris Brannon
2014-01-17 12:09 ` Adam Thompson
2014-01-17 18:42 ` Chris Brannon
-- strict thread matches above, loose matches on Subject: below --
2014-01-07 12:08 Adam Thompson
2014-01-07 12:10 ` [Edbrowse-dev] js progress update1 Adam Thompson
2014-01-08 10:03 ` [Edbrowse-dev] js progress update Adam Thompson
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=20140108124047.GB3935@toaster.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).