unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Alex Branham <alex.branham@gmail.com>, emacs-devel@gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Warning "Obsolete name arg "password-store" to constructor auth-source-backend"
Date: Mon, 12 Feb 2018 11:12:57 -0500	[thread overview]
Message-ID: <a561418b-3c6f-9c59-de89-48078475d44a@gmail.com> (raw)
In-Reply-To: <87vaf2nsq0.fsf@gmail.com>

On 2018-02-12 10:16, Alex Branham wrote:
> Hi all -
> 
> I'm seeing the following warning when byte compiling
> auth-password-store[1] on Emacs 26:
> 
>  auth-password-store.el:82:1:Warning: Obsolete name arg "password-store" to
>       constructor auth-source-backend
> 
> Does anyone have any idea what this could mean or how to fix it? I
> raised this in a github issue[2] and the package's authors seem as
> perplexed as I am.

Yes, see 2a61bd0096db23123734db439051c859e42b9606:

    ** EIEIO
    …
    *** The `newname' argument to constructors is optional&deprecated.
    If you need your objects to be named, do it by inheriting from `eieio-named'.

It comes from passing "password-store" to auth-source-backend.

Looks like Damien silenced that warning in auth-source-pass.el:

(defvar auth-source-pass-backend
  (auth-source-backend
   (format "Password store")
   :source "." ;; not used
   :type 'password-store
   :search-function #'auth-source-pass-search)
  "Auth-source backend for password-store.")

… which seems OK to do, since all callers of auth-source-backend in auth-source.el do it?  Maybe Stefan (who wrote that warning) can advise?

Clément.



  reply	other threads:[~2018-02-12 16:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 15:16 Warning "Obsolete name arg "password-store" to constructor auth-source-backend" Alex Branham
2018-02-12 16:12 ` Clément Pit-Claudel [this message]
2018-02-12 16:26   ` Stefan Monnier
2018-02-12 17:17     ` Alex Branham

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=a561418b-3c6f-9c59-de89-48078475d44a@gmail.com \
    --to=cpitclaudel@gmail.com \
    --cc=alex.branham@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).