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] Back to C
Date: Sat, 27 Dec 2014 06:43:28 -0500	[thread overview]
Message-ID: <20141127064328.eklhad@comcast.net> (raw)

With some help from Adam, edbrowse is entirely back to C.
I even changed the bool true false stuff back.
This was easy for me because of a program I wrote many years ago
called sedunit, like sed but it only replaces logical units.
If you ask to change foo it won't change foobar.
So I just type

sedunit *.[chp] <<!
eb_bool/bool
eb_true/true
eb_false/false
!

and it's done.

Also got rid of the extern "C" {} in eb.p, don't need that any more.
That means eb.p can be indented, if you wish,
and it will come out properly.

Well I didn't mention in my list of tasks to track down the seg fault in js.
Sorry to hear you are plagued by that again Adam.
Does the hello world program run?
That would be a good test.

If nobody else is jumping on it, I may look into the download
in background task, cause I think it should be straightforward.
We don't need a lot of ipc communications, just fork and run in background
and tell user when done.
I'd go along with Adam on having some kind of download directory,
cause as he says, you can always type ./foo, and even more than that,
you can omit the download directory from the config file,
and then you just don't have one, if that's your preference.
I thought about spawning a curl command to do the download,
that's easy programming,
but someone on this llist pointed out that some sites
require you to step through some javascript to actually make the download work,
which curl is never going to understand,
so the only way to cover this case is to start the download as usual,
then switch to another curl callback function that writes
the chunks of data to a file,
instead of adding them to a growing buffer in memory.

Karl Dahlke

             reply	other threads:[~2014-12-27 11:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-27 11:43 Karl Dahlke [this message]
2014-12-27 19:31 ` Adam Thompson
2014-12-28 11:50   ` 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=20141127064328.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).