-
Notifications
You must be signed in to change notification settings - Fork 165
Prompt for SSH passphrases in minibuffer #1207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@progfolio Big news! |
Cool! |
Huh, why would it fail without |
Apologies. It looks like the repository does clone, but a warning is generated: ⛔ Warning (straight): Could not check out branch "[email protected]:progfolio/tunic.git" of repository "tunic" process log output: Enter passphrase for key '/home/n/.ssh/id_ed25519': ********
* remote origin
Fetch URL: [email protected]:progfolio/tunic.git
Push URL: [email protected]:progfolio/tunic.git
HEAD branch: master
Remote branch:
master tracked
Local branch configured for 'git pull':
master merges with remote master
Local ref configured for 'git push':
master pushes to master (up to date)
[Return code: 0]
$ cd /tmp/straight.test/straight/repos/tunic/
$ git checkout -B git\@github.com\:progfolio/tunic.git origin/git\@github.com\:progfolio/tunic.git
fatal: 'origin/[email protected]:progfolio/tunic.git' is not a commit and a branch '[email protected]:progfolio/tunic.git' cannot be created from it
[Return code: 128] My hunch is that |
Huh, yeah, that's completely bricked. It thinks the remote URL is a branch name. Could be an issue where the output format changes when Git thinks it can talk to stdin, which also caused an issue when I was listing branches (d036862). Looking at your process buffer output something looks scuffed there, I suspect this is the issue and you have found a bug. I will check on it further. |
Ahaha! I know what the issue is. Look at this code: Lines 3018 to 3022 in 148611e
It's checking the 4th line of the The answer is to do more robust parsing, of course. I'll update the command that this is using. |
That makes sense. The stdout could be offset by multiple lines, too, in the case of a retry after a bad password. |
That should be fixed in #1212. |
Confirmed! |
It's finally here. Six years in the making. Closes #334. Replaces 00ee2d4 and f18e581. Fully compatible with the new process management API. Handles stdout and stderr properly.
Use
(setq straight-display-subprocess-prompts t)
to opt in and test it out.