All gist functions result in: Wrong type argument: stringp, nil about gist.el

[rgrinberg]

Same problem here.

[marcinant]

👍

1. I got gh profile configured and set.
2. gist keeps to ask for username and password (why?)
3. Some error reports I get:

gh-url-set-response: Changing multibyteness in a narrowed buffer
Contacting host: api.github.com:443
byte-code: Wrong type argument: listp, "https://developer.github.com/v3"

user-error: End of history; no default available
byte-code: JSON readtable error

eieio-validate-slot-value: Invalid slot type: gh-gist-api, :base, string, nil

[cb0]

For emacs 24.3.1 x86_64-pc-linux-gnu I also recieve.
"Wrong type argument: listp, "https://developer.github.com/v3"" while doing initial gist-list.
Currently unable to use it at all. Removing, installing ... did not work.

Like @marcinant, I also get the password/username question all the time. :(

[slackorama]

@cb0: I had the same "wrong type argument listp" problem in emacs 24.4.1. I fixed it by re-installing all my elpa packages. YMMV.

[sigma]

I'm unable to reproduce, but there I've seem weird issues that seem to suggest that eieio underwent some changes that require getting rid of old .elc files. You might wanna try that... :/

[cb0]

I'm still unale to use it. That's the detail error, maybe someone can see what's wrong.

Contacting host: api.github.com:443
Opening TLS connection to `api.github.com'...
Opening TLS connection with `gnutls-cli --insecure -p 443 api.github.com'...failed
Opening TLS connection with `gnutls-cli --insecure -p 443 api.github.com --protocols ssl3'...failed
Opening TLS connection with `openssl s_client -connect api.github.com:443 -no_ssl2 -ign_eof'...done
Opening TLS connection to `api.github.com'...done
byte-code: Wrong type argument: listp, "https://developer.github.com/v3"

[mfiano]

I get this error:
byte-code: Wrong type argument: listp, "https://developer.github.com/v3"
with emacs 24.5 using latest MELPA package and dependencies.

[Emantor]

I fixed it by moving the gitconfig entry for token to token-oauth, I think the github blog entry which is referenced in the Readme is way to old (from 2008...) and the config sytnax has changed now.

[torgeir]

Seeing the same thing as @Axionix after being prompted for username/password, on 24.5 with latest off melpa