unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Leon Vack <dev@lgcl.de>
To: Olivier Certner <ocert.dev@free.fr>
Cc: larsi@gnus.org, 45340@debbugs.gnu.org, bandali@gnu.org
Subject: bug#45340: erc-services.el: Auth-source support for passwords
Date: Wed, 20 Jan 2021 11:42:05 +0100	[thread overview]
Message-ID: <87o8hj28le.fsf@sol.hw.lgcl.de> (raw)
In-Reply-To: <1936038.bl7DLxgNLY@ravel>



Hello Olivier,

sorry for the long time it took me to reply.

Olivier Certner <ocert.dev@free.fr> writes:

> I also have some further suggestion, beyond this enhancement. I think it would 
> be even more useful that `erc-prompt-for-nickserv-password' is not required to 
> be nil for auth source (or `erc-nickserv-passwords', for that purpose) to be 
> used, but rather that, if search in `erc-nickserv-passwords' and auth source 
> (if enabled) fails, then prompting should be used as a last resort (if 
> enabled). I think this would cover all the use cases I can think of (with 
> proper settings of `erc-prompt-for-nickserv-password' and `erc-use-auth-
> source-for-nickserv-password'). If more customizations are required, or just 
> for the sake of 'simplicity' (YMMV), than maybe replacing these booleans with 
> a single list indicating the means to get the password and their order could 
> be nice.
>
> What do people think?
>

I personally agree with you on this. Having to change
`erc-prompt-for-nickserv-password' for `erc-nickserv-passwords' to have
an effect caught me off guard in the beginning as well.

The list of NickServ password sources seems like the more flexible
solution, but would be a bit more complex to implement, considering how
the current system works. Changing the precedence to
`erc-nickserv-passwords', auth source and then prompt (if enabled), on
the other hand, should be a rather simple patch.

I think we should discuss this not on this bug, but on the emacs-erc
mailing list before we change that.

Regards,
Leon Vack





  reply	other threads:[~2021-01-20 10:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20 10:54 bug#45340: erc-services.el: Auth-source support for passwords Leon Vack
2020-12-21  4:46 ` Lars Ingebrigtsen
2020-12-21  5:44   ` Leon Vack
2020-12-29  0:12 ` Amin Bandali
2020-12-29  8:24   ` Leon Vack
2021-01-09  7:22     ` Leon Vack
2021-01-10 11:49     ` Lars Ingebrigtsen
2021-01-11 14:38       ` Leon Vack
2021-01-11 14:51         ` Lars Ingebrigtsen
2021-01-11 16:04           ` Leon Vack
2021-01-11 16:06             ` Lars Ingebrigtsen
2021-01-15  9:46               ` Olivier Certner
2021-01-15 11:10                 ` Leon Vack
2021-01-15 12:41                   ` Olivier Certner
2021-01-20 10:42                     ` Leon Vack [this message]
2021-01-13  8:27 ` bug#45340: foo Richard Copley
2021-01-15 21:48   ` Basil L. Contovounesios

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=87o8hj28le.fsf@sol.hw.lgcl.de \
    --to=dev@lgcl.de \
    --cc=45340@debbugs.gnu.org \
    --cc=bandali@gnu.org \
    --cc=larsi@gnus.org \
    --cc=ocert.dev@free.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).