edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Disabling local echo for password fields
Date: Wed, 12 Jul 2017 08:11:15 +0200	[thread overview]
Message-ID: <20170712061115.GA3270@nautica> (raw)
In-Reply-To: <87tw2joaop.fsf@the-brannons.com>

Chris Brannon wrote on Mon, Jul 10, 2017:
> The inp_types list in decorate.c is also duplicated in html.c, and you
> missed that one in the patch to add the new minor type.
> Couldn't we just get rid of the inp_types from html.c and make inp_types
> from decorate.c global?

I have done just that: removed inp_types in html.c and declared as
extern in eb.h
I think 'number' might also need to be moved to minor, but did not take
the time to change that.

> I'd also say that the function infShow needs to be reworked a little, so
> that it shows the minor type, and not just text.
> I'd like Karl's opinion on that.  If he agrees, I wouldn't mind doing
> that work after your patches are submitted.

That would make sense to me, I have made both inp_types and inp_others
global at the same time so you will be able to use it.

> Aside from all of that, your patchset looks pretty good.
> I still want Adam's opinion on the auth negotiation.  I don't know if
> his issue still exists, or whether it was subsequently fixed by libcurl
> / other software.

I have repushed the series without the last curl auth negotiation patch,
so we are not held by that. The patch is still available in my master
branch on github ( https://github.com/martinetd/edbrowse )

I have also added a first draft to the userguide, both in English and
French, for the new command.
We cannot change the command name once this is merged so now is a good
time to complain about my naming sense!


-- 
Dominique

  reply	other threads:[~2017-07-12  6:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03  5:19 Dominique Martinet
2017-07-03 11:29 ` Karl Dahlke
2017-07-07 12:13   ` Chris Brannon
2017-07-07 13:35     ` Dominique Martinet
2017-07-09 14:40   ` Dominique Martinet
2017-07-09 15:45     ` Karl Dahlke
2017-07-09 21:45     ` Karl Dahlke
2017-07-10  4:56       ` Dominique Martinet
2017-07-11  4:32         ` Chris Brannon
2017-07-12  6:11           ` Dominique Martinet [this message]
2017-07-12 12:27             ` Chris Brannon
2017-07-12 12:55               ` Dominique Martinet
2017-07-12 14:32                 ` Chris Brannon
2017-07-12 15:02                   ` Dominique Martinet
2017-07-12 22:00                     ` Chris Brannon
2017-07-12 16:56                   ` Karl Dahlke
2017-07-12 12:44             ` Karl Dahlke
2017-07-15 11:29               ` Dominique Martinet
2017-07-15 12:27                 ` Chris Brannon
2017-07-15 23:42                   ` Karl Dahlke
2017-07-16  2:22                 ` Chris Brannon
2017-07-17 14:04                 ` Chris Brannon
2017-07-17 14:39                   ` Dominique Martinet
2017-07-17 14:45                     ` 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=20170712061115.GA3270@nautica \
    --to=asmadeus@codewreck.org \
    --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).