On Fri, Dec 30, 2011 at 05:40:47AM +0100, Sven Strickroth wrote: > >> git-core also asks for username using *_ASKPASS, this is the reason why > >> I implemented it this way. I noticed it when I tried to push to google > >> code (using https). > > > > I thought that was updated with Peff's series recently? > > So, was this changed? git-core doesn't ask for a username using > *_ASKPASS helpers anymore? No, it will. It's only that we will echo characters when using the terminal prompt. In theory we could have an ASKPASS-style interface that would would echo characters, but there's no such interface in common use (i.e., we would have to invent it). > I talked off-list with Junio and he proposed to use another environment > variable (e.g. GIT_DIALOG for a different tool) to solve these issues. > > A good way could be to define the GIT_DIALOG-tools to have two > parameters. First (pass|text|filename|...) with fallback to text, this > way one can implement a password field, a text field, a file chooser (on > type filename) and it is still extendable for e.g. directory choosers > (if we might need that)... Yes, like that. I think some windowing toolkits already have programs to provide dialogs from shell scripts. You might look at them for inspiration on the interface. For credentials, it would be nice to be able to create a multi-field dialog, like: Username: <text input> Password: <text input> Remember password? [checkbox] I was planning to do something custom for credentials as an extension to the credential helper protocol, but this could also fall under the heading of a general prompt helper. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html