You also have to
Explicitely enable loopback mode for pinentry in your
Configure epa to use loopback for pinentry.
Start the pinentry server in emacs,
1. Enable Emacs pinentry and loopback mode for gpg-agent
Put this in your ~/.gnupg/gpg-agent.conf:
Then tell gpg-agent to load this configuration ...
In Shell mode, Emacs detects password prompts based on the prompt. If it sees Password: (or Enter new password:, or Passwort:, or Wachtwoord: or a number of variations), it assumes that you're prompted to enter a password and reads a string from the minibuffer (repeating the prompt); this string is not echoed and is not entered in any history list.
If Emacs ...
As you have noticed, you can yank the password when Magit is reading
it in the minibuffer (this works pretty much always when user input is
read in the minibuffer for whatever purpose). So the sequence is more
P P RET
This might or might not cache the password, depending on various
settings. First you need to tell Git to cache the ...
I use a simple password manager called pass. It offers a simple command line interface with is ideal for integrating with Emacs. The backing store is a GPG encrypted GIT repo. It actually ships with an Emacs package although I don't use it. My interface is laughably simple:
(defun my-fixup-gpg-agent (frame)
"Tweak DISPLAY and GPG_TTY environment variables ...
Have you tried installing gpg version greater than 2.1, and then (setq epa-pinentry-mode 'loopback)? This should prompt for the password in the minibuffer.
epa-pinentry-mode has been marked obsolete from Emacs 27. Use epg-pinentry-mode instead.
Configure comint-password-prompt-regexp so that it includes whatever text pass gives at the second prompt.
Alternative answer, instead of just typing the password, you could type M-x send-invisible RET enter-the-password RET.
Edit ~/.ssh/config so that it contains the following:
Then whenever magit asks git to ask ssh to talk to github.com, ssh will know what key to use; saves a lot of mucking about.
The reason you were asked for your password was that apt-get install was being invoked to install the additional software (poppler and friends) needed by pdf-tools.
1) Is this typical?
No -- the vast majority of elisp packages do not attempt to automatically install other system requirements. It's not uncommon for other system software to be required by ...
Tramp uses the auth-sources backend for managing passwords. It needs some specialized entries in .authinfo, like
machine melancholia port scp login daniel password geheim
Read the Tramp manual, chapter "Password handling", for details.
auth-sources have also some functionality to create password entries on-the-fly. I've never tried this functionality ...
I am moving my comment to an answer explaining how pinentry-emacs works because of formatting
pinentry-emacs stops the window from popping up that asks for your password and insteads asks for your password through the minibuffer.
It is super poorly documented and took me a bit of time to set up. From what I can tell I placed
I use pass to store my passwords, and a lisp wrapper to set the value appropriately:
(defun my-password (pass)
(concat "pass show " pass))))
(setq my-jabber-password (my-password "Personal/jabber"))
This was intended as a comment, but it's too long, hopefully it will give you some hints.
Right now I don't have a mac to try OSX configs, but this is what I have now:
In short, I had an incorrectly configured ~/.authinfo that causes Tramp to automatically send a default password (which was the incorrect password). Deleting ~/.authinfo resolved my issue.
An incorrectly configured ~/.netrc can also cause this same issue. So make sure to check whether a .authinfo or .netrc file exists, and ensure that it is not submitting ...
If the account you're trying to log in with uses some weird fancy shell prompt, then there is a good chance that this is what makes tramp trip.
One way to test it: Log in as root, then enter
(that's a normal, standard shell (ZSH, BASH, younameit) prompt, one that tramp will understand)
then switch to the user account, and launch emacs -q (to ...
A few days ago I reported a bug against Emacs for this very problem (bug 19074). If you're comfortable doing so, I'd suggest applying the patch I supplied - and please report back with your results so I can fix any problems :)
I didn't know about `auth-source-search, so I wrote this code instead, in order to extract a password from the keychain:
(defun get-keychain-password (service)
"Get a generic password from the OS X keychain.
The password is associated with the string SERVICE.
This corresponds to the Account field in the Keychain Access GUI.
BUG: If there is no matching ...
The issue seems to be the inability of Emacs 24.3 to handle RSA token passcode request. To solve this issue I upgraded to Emacs 24.5 employing Linuxbrew as follows
brew install linuxbrew/xorg/xorg
brew install emacs --with-x11 --with-gnutls
This enabled the installation of Emacs 24.5 in the ~/.linuxbrew path which now prompts for the passcode and in turn ...
The issue seemed to have something to do with ido, so I added Option B from here and it works great.
(defadvice ido-find-file (after find-file-sudo activate)
"Find file as root if necessary."
(unless (and buffer-file-name
(find-alternate-file (concat "/sudo:root@localhost:" buffer-file-name))))