-
Notifications
You must be signed in to change notification settings - Fork 6
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
emacs-lastpass and magit doesn't play well together #9
Comments
I believe having users calling that function and backends returning that function is what |
I have no more experience with
(Emphasis mine) My take, from reading that, is that the Regardless it seems to me that |
Thanks for providing some pointers. As soon as I get back to my Linux computer I'll check it out! |
I have interpreted "can" as "if the backend supports storing passwords persistently, then it must return a function so that the caller can call that if and only if it wants to do that. Otherwise it cannot, and therefore does not have to, return such a function." With that interpretation But there are at least two third-party backends that just save the secret instead of a saver function, so I'll probably handle that case in |
I got all this working with the new forge package. My guess is that |
Yes, I changed something in |
Hi!
I was trying to use the
emacs-lastpass
integration withauth-source
to be able to store the github OAuth token that is created when setting up a github account with magit.I get a
Symbol's function definition is void: nil
which I've tracked down to this line in ghub.el.I'm not sure if this is a bug in
emacs-lastpass
or inghub
so I'm putting the issue here and pinging in @tarsius .The text was updated successfully, but these errors were encountered: