Re: bug#29108: 25.3; ERC SASL support

Akib Azmain Turja <[email protected]> writes:

> "J.P." <[email protected]> writes:
>
> [...]
>> Also, I've been trying to get a hold of you regarding another bug:
>
> Just out of curiosity, why me?  Is it because I use pass?

Because you took to emacs-devel to air your frustrations and share some
code, which made me hopeful that you might be willing to direct that
energy toward solving these problems in a productive and practical way.

>>   https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58985
>
> Hmm, looks like I was CC'ed, but I didn't notice.  :(
> I will try to review the patches.

I also replied directly to your initial email on emacs-devel:

  https://lists.gnu.org/archive/html/emacs-devel/2022-11/msg00334.html

> Yeah, auth-source-pass is indeed just a hack, a terrible one.  I needed
> to apply a few advices on that auth-source-pass make it work at least
> reasonably well for me uses.
>
> Fix auth-source-pass will require the existing API of it (which the
> Emacs package "pass" uses) and may even need complete rewrite.

I didn't realize that the Melpa package pass required password-store
(and thereby auth-source-pass). TIL.

> But Adam Porter (CC'ing), the maintainer of ement.el (available on GNU
> ELPA), a Matrix client, claims that auth-source is from the dark side[1]
> and refused to support it claiming it's not suitable for general use[2].

If you don't mind, I'd rather not discuss any gripes you may have with
auth-source generally on this bug thread. And please direct any further
discussion regarding both auth-source-pass and (to whatever extent it's
relevant) auth-source, to bug#58985. Thanks.

>> Based on your email to the devel mailing list, it seems you have some
>> experience (or at least opinions and interest) in that area. Please take
>> a look if you haven't already, and then volunteer to help get some
>> improvements in tree before Emacs 29 is cut.
>
> Thanks for the reminder, otherwise I would have just missed that
> discussion.
>
> Anyway, when the Emacs 29 branch is going to cut?  I have some changes
> (semantic highlighting of code) waiting to merge to Eglot (now in core)
> for about six months.  I have got the paperwork to sign about ten days
> ago, but due to some (personal) problems it's taking some time to sign
> it.  I really want to make it into Emacs 29, instead of 30.

All I've heard is that Emacs 29 will be cut "later this month."
Regarding your paperwork situation, I feel your pain but sadly have
nothing useful say on the matter (not that this bug thread is the right
place for that).

>> Also, I've noticed someone on Libera with the nick akib pop into #erc on
>> occasion. Please don't hesitate to say hi if that was in fact you.
>
> Yeah, that's indeed me.

Cool.