From: Olivier Certner <ocert.dev@free.fr>
To: 46777@debbugs.gnu.org
Subject: bug#46777: 28.0.50; ERC: NickServ identification: Prompt for password after other sources, overall simplifications
Date: Thu, 25 Feb 2021 18:33:53 +0100 [thread overview]
Message-ID: <5495728.XOh7uYVVfo@ravel> (raw)
When `erc-prompt-for-nickserv-password' is true, don't ignore the
other forms of identification. Instead, process them first, and
prompt for the password last. Separate concerns (determination of the
nick to use, of the password to use, and actual message sending).
Note that the user can be interactively prompted for a password on
reception of a Nickserv request, as before (on
`erc-prompt-for-nickserv-password').
This is a follow-up to #45340 (see end of discussion there for additional
context).
Pull request with the single commit to be posted after the bug is open.
Changes rebased on master.
--
Olivier Certner
next reply other threads:[~2021-02-25 17:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 17:33 Olivier Certner [this message]
2021-02-25 17:38 ` bug#46777: 28.0.50; ERC: NickServ identification: Prompt for password after other sources, overall simplifications Olivier Certner
2021-02-25 17:47 ` Basil L. Contovounesios
2021-02-25 18:22 ` Olivier Certner
2021-06-08 2:23 ` J.P.
[not found] ` <878s3l6qms.fsf@neverwas.me>
2021-06-09 13:30 ` Olivier Certner
2021-06-10 3:59 ` J.P.
2021-07-06 14:52 ` bug#46777: Updated patch Olivier Certner
2021-07-22 12:29 ` bug#46777: 28.0.50; ERC: NickServ identification: Prompt for password after other sources, overall simplifications Lars Ingebrigtsen
2021-07-30 12:27 ` Amin Bandali
2021-07-30 12:43 ` Lars Ingebrigtsen
2021-07-26 7:39 ` J.P.
[not found] ` <87sg01jzgk.fsf_-_@neverwas.me>
2021-09-14 9:20 ` J.P.
2021-09-16 5:30 ` Amin Bandali
[not found] ` <87v931cck5.fsf@gnu.org>
2021-09-16 12:42 ` Lars Ingebrigtsen
2021-09-17 4:45 ` Amin Bandali
[not found] ` <87a6kbn72z.fsf@gnu.org>
2021-09-17 7:57 ` Olivier Certner
2021-09-19 15:26 ` Amin Bandali
2021-09-17 2:16 ` J.P.
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=5495728.XOh7uYVVfo@ravel \
--to=ocert.dev@free.fr \
--cc=46777@debbugs.gnu.org \
/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).