From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] novs
Date: Fri, 5 Sep 2014 19:39:35 +0100 [thread overview]
Message-ID: <20140905183935.GB3563@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <87r3zqaurr.fsf@mushroom.PK5001Z>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
On Fri, Sep 05, 2014 at 09:37:12AM -0700, Chris Brannon wrote:
> Karl Dahlke <eklhad@comcast.net> writes:
>
> > Would it help to have a novs directive in the config file,
> > somewhat like nojs?
Plus 1 from me.
> I like it. From a security standpoint, using novs for unimportant sites
> that you can prove are broken is better than the vs toggle. The vs
> toggle is all-or-nothing. I'm very forgetful. If I turn it off to
> visit some site with a self-signed cert, odds are good that I'll forget
> to reenable it once I'm done with that site. I'm probably not the only
> one. I'd also argue for a novs command that could be entered from
> edbrowse's command mode.
Same here, I often use it then forget to switch verification back on.
Rather than a novs command, I'd rather have the novs configuration directive
and a command to reload the config file (possibly without running the init
function) without restarting the browser.
There's been a number of times I've wanted to do this, nojs, proxy settings,
adding functions which I then want to run etc. Obviously this is a big feature potentially,
but I think it'd be worth doing. I'd be willing to invest some time in this if anyone else wants it.
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-09-05 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 3:08 Karl Dahlke
2014-09-05 16:37 ` Chris Brannon
2014-09-05 18:39 ` Adam Thompson [this message]
2014-09-09 14:34 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=20140905183935.GB3563@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=chris@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).