Re: Secrets API "login" session is now "Login"?

[Michael Albinus]

Ted Zlatanov <address@hidden> writes:

> This morning I noticed that while seahorse told me the login collection
> was "login", the Secrets API listed it as "Login".  I'm 100% sure that
> it used to be "login".
>
> I've adjusted auth-source.el and auth.texi accordingly.  If that's
> wrong, please let me know.

The Secret Service API does not speak about the "login" collection. The
only promise it gives is the "default" alias:

"Client applications without special requirements should store in the
 default collection. The default collection is always accessible through
 a specific object path."

> Ted

Best regards, Michael.