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]  URL assert
Date: Fri, 25 Apr 2014 11:25:16 +0000	[thread overview]
Message-ID: <20140325112516.eklhad@comcast.net> (raw)

> Are any other classes effected?

No. I checked.
One of those cut & paste things,
I copied the window class struct to build the url class,
and the global flag went along for the ride, and it shouldn't have.
I was happy it was a trivial fix, not a major error in logic or structure.

The new smtp pop3 machinery is in place, using the curl library,
which we were already using for http and ftp anyways.
Thanks to Chris.
Saves about 1200 lines of code, is easier to read,
is maintained by someone else,
and provides some new features that I don't have to reinvent.
ipv6 mail servers, various authentication algorithms, etc,
but I wonder if we haven't lost the ability to cc,
rather than a straight recipient.
I just thought of that now, as I write this. Hmm.
I suppose I could live without cc, but it's nice sometimes.
Chris what do you think here?

Another thing we save is 52 messages, in messages.c, that aren't needed any more.
I changed these to NotUsed1 through NotUsed52 in messages.h.
This was easier than deleting them, and deleting, perfectly,
the corresponding strings in all the languages we support.
So if you need a new message in the future, glom onto one of the NotUsed
messages and take it over, in its position.
I guess we lost 52 messages because I use the curl messages for everything now,
and there are fewer of them anyways than my home grown software.

On we go.

Karl Dahlke

             reply	other threads:[~2014-04-25 15:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 11:25 Karl Dahlke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-24 14:40 Karl Dahlke
2014-04-25 14:27 ` Adam Thompson
2014-04-23 14:54 Karl Dahlke
2014-04-24  9:02 ` 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=20140325112516.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).