unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Damien Cassou <damien@cassou.me>
Cc: alex.branham@gmail.com, Nicolas Petton <nicolas@petton.fr>,
	30900@debbugs.gnu.org
Subject: bug#30900: 26.0.91; auth-source-pass-enable results in customization type mismatch for auth-sources
Date: Mon, 02 Apr 2018 08:56:39 -0400	[thread overview]
Message-ID: <87po3hg41k.fsf@lifelogs.com> (raw)
In-Reply-To: <871sgb5goy.fsf@cassou.me> (Damien Cassou's message of "Fri, 23 Mar 2018 09:39:25 +0100")

On Fri, 23 Mar 2018 09:39:25 +0100 Damien Cassou <damien@cassou.me> wrote: 

DC> Eli Zaretskii <eliz@gnu.org> writes:
>>> > Using the new (26.0.91) auth-source-pass-enable function modifies the
>>> > auth-sources variable to something isn't specified in :type, resulting
>>> > in a type mismatch when looking at the customize-variable buffer for
>>> > auth-sources.
>>> 
>>> Presumably this auth-sources setting also doesn't work in the next Emacs
>>> instance, unless one manually loads the auth-source-pass library?

DC> I think we should sync with Ted, in CC, so that auth-sources
DC> customization type allows external providers. What do you think Ted?

IIUC, we have external providers for the auth-source backends but the
customization types of `auth-sources' are not extensible by the
providers.

I can think of two approaches. We can either allow a typeless
configuration (in addition to the built-ins) to make it easier to
customize any way the user wants, or we can make the :type extensible.
I'm not sure if there's a standard way of doing this in Emacs but if
there is, I'd use it. If not, the typeless approach is probably easier
to support and less surprising.

Ted





  parent reply	other threads:[~2018-04-02 12:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 22:32 bug#30900: 26.0.91; auth-source-pass-enable results in customization type mismatch for auth-sources Alex Branham
2018-03-21 23:52 ` Glenn Morris
2018-03-22  7:36   ` Eli Zaretskii
2018-03-22 10:12     ` Nicolas Petton
2018-03-23  8:39     ` Damien Cassou
2018-04-01  9:11       ` Eli Zaretskii
2018-04-02 12:56       ` Ted Zlatanov [this message]
2018-04-03 13:34         ` Damien Cassou
2018-04-04 18:16           ` Ted Zlatanov
2018-04-04 19:17             ` Eli Zaretskii
2018-04-04 21:32               ` Ted Zlatanov
2018-04-04 22:00                 ` Glenn Morris
2022-04-17 10:39                   ` Lars Ingebrigtsen
2018-04-05  6:06                 ` Eli Zaretskii
2018-04-05 10:03               ` Glenn Morris
2018-04-05 10:21                 ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87po3hg41k.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=30900@debbugs.gnu.org \
    --cc=alex.branham@gmail.com \
    --cc=damien@cassou.me \
    --cc=nicolas@petton.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).