From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] bug with the latest changes
Date: Sun, 18 Jan 2015 11:01:20 -0500 [thread overview]
Message-ID: <20150018110120.eklhad@comcast.net> (raw)
Ok - 2 minutes after I sent the last email,
I caused the bug to happen, ironically, by turning js off.
Now that's a switch, a seg fault that only happens without js.
I'll check it out today as time permits.
Karl Dahlke
next reply other threads:[~2015-01-18 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 16:01 Karl Dahlke [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-18 15:58 Karl Dahlke
2015-01-18 15:26 Chris Brannon
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=20150018110120.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).