From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?B?Sm/Do28gVMOhdm9yYQ==?= Newsgroups: gmane.emacs.devel Subject: Re: What to do about unmaintained ELPA packages Date: Tue, 31 May 2022 23:08:01 +0100 Message-ID: References: <87k0a42fc9.fsf@posteo.net> <8a6d74f7-b78f-3dad-1bd5-f41354f4391f@yandex.ru> <871qwb5wxv.fsf@posteo.net> <87bkvd4ps5.fsf@posteo.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000004af3ef05e055fd33" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13669"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Monnier , Dmitry Gutov , emacs-devel , Noam Postavsky To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jun 01 00:16:25 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nwAA5-0003Mh-1B for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Jun 2022 00:16:25 +0200 Original-Received: from localhost ([::1]:46756 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nwAA3-000144-H2 for ged-emacs-devel@m.gmane-mx.org; Tue, 31 May 2022 18:16:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56164) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nwA0s-0000fs-27 for emacs-devel@gnu.org; Tue, 31 May 2022 18:06:55 -0400 Original-Received: from mail-oa1-x2c.google.com ([2001:4860:4864:20::2c]:36310) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nwA0p-000651-VI for emacs-devel@gnu.org; Tue, 31 May 2022 18:06:53 -0400 Original-Received: by mail-oa1-x2c.google.com with SMTP id 586e51a60fabf-edeb6c3642so273282fac.3 for ; Tue, 31 May 2022 15:06:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ubw5i4mYThKjcOaLPLH8uH7jRvPbWNzsbIkD1UDl6p8=; b=Rez99o0Jby/tCoi/8DXc83Rn9d3g6Jkm/9tUsTv7IwLJ/Zf72Ms3olpYsxWTqcvurk OF/5mYj4F4DSfdJudFJs46SmaSJlln1w/XRNrYySack9cUv9AfJa1drzt3yZJQ9wmdX+ B+SJqkxr1hSd6JqQ6iK6mAzpOSFhb0B9bA8JWtLPwiRI32yesuhdWevwihz3UfYfby4e pwIKRZLuoWLXc4ohsQANH1LSwzEtJWe38qPPVfeyQyZYJ/mZa4tKzEALgL/X4T2NLoCI LWO7cdX4bN+p5Jtdqs1ct7B4Wd/QqcjxZ91RolBXi0vYBg5q1vK9afLcmMVKuOjOtf0+ R3gA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ubw5i4mYThKjcOaLPLH8uH7jRvPbWNzsbIkD1UDl6p8=; b=hH7nX891h1lvG+Zu/aV5sNGOyQpWCOMxQcMH5shR0qmOegrNl48V9Li26lpH58dGA0 moKL6CT9zGPBzFKRFwVCts00/Amy6IpT7g71GlYAgwEGR4D8oGvmKXyfqO/jqrux76sQ wpte1YDCc6S9FMvcBftjJxpYcU7QTXuIksuQCEYOEWgC+WQTZ1xKVFb5YoOj2E98rbJc Y1l8MjdjIo05YPU4oBQylt/rfD+B8V+ibMt1pR7NKAegUOAjYzPABOldHCk5yjJ7Uz2v aJyRQ5i4pCKgnkgxlfzvvdJPWjTMIf8iSpu7I4VZ62GffjcI4g26wEcly6wPE2TLEAxC m+Tw== X-Gm-Message-State: AOAM533CWlNEG+avs6unBY0Op83gbOwKR4m4OxUAgUjFO3aHpNRF6X7I t38EkdrU9Zrv/qWuCRLti9sRod3r9HfOcrv301Q= X-Google-Smtp-Source: ABdhPJy9H7nW4ckjXdWvdjmDttMMDxfbsVKgN7lHSJDEcHhbbj8BPAPEMomuOg0h+QAYZMDzDyxGa5rATwhUCj5IJuk= X-Received: by 2002:a05:6870:b003:b0:f2:3989:7817 with SMTP id y3-20020a056870b00300b000f239897817mr14431665oae.209.1654034809941; Tue, 31 May 2022 15:06:49 -0700 (PDT) In-Reply-To: <87bkvd4ps5.fsf@posteo.net> Received-SPF: pass client-ip=2001:4860:4864:20::2c; envelope-from=joaotavora@gmail.com; helo=mail-oa1-x2c.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:290451 Archived-At: --0000000000004af3ef05e055fd33 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, May 31, 2022, 17:42 Philip Kaludercic wrote: To be specific, my issue was mentioned here: > https://github.com/joaotavora/yasnippet/issues/1121 ("Avoid > false-positives when expanding snippets"). In my case, I have managed > to circumvent the issue by unbinding the tab key and relying in > hippie-expand, but the solution is not elegant and I would have > appreciated a discussion on the issue tracker. > Does it really matter where the discussion happens? The problem here is not the place, it's the unavailability of brain-hours to dedicate to your request. The point was not to say that yasnippet has been abandoned, just to give > an example where the liveliness of development could be questioned. > You don't have to sugar-coat it. Yasnippet's bug reports have gone unanswered at least for a year. They don't make it into my inbox, I'm not the maintainer anymore. Noam did a thorough and excellent job while he was maintaining it, he's not available anymore. It's de facto unmaintained, though rather stable in its intended use case. Of course Emacs is gigantic and everyone wants everything, and so it might not be doing what you want. I understand that. In that sense, it'd be nice if yasnippet wasn't' the monolithic package it is, and 'snippet.el' is a step in that direction. Then you could perhaps opt out (or in) to the multi-file, keybinding, abbrev-like functionality of yasnippet.el. Or simply compose 'snippet.el' bare-bones expansion/navigation with whatever other productivity tool where you think snippets make sense. Eglot is one of those tools and it works well with yasnippet today. I'd love to make it depend on simply 'snippet.el'. > Is it just the general idea of abandonment of the fact that people's > > issue reports go unanswered? If the latter, then I think archiving to > > the repo would make sense. No more issue reports would come in and > > one could advertise the Emacs bug tracker. Would that improve things? > > I guess, but I think it would be preferable to call for someone to fork > the package instead of shifting the burden of maintenance onto the emacs > bug tracker. > Again, i don't quite understand how that magically solves the root problem You're free to fork when you want, of course, but that normally happens when you want to take the software in a new irreconcilable new direction. Currently, yasnippet just needs (1) a maintainer that understands the current functionality and "protects" it, fixing bugs, not introducing new ones. New features are probably not a great idea. (2) someone to develop 'snippet.el' into production-ready state and make 'yasnippet.el' depend on it, then may integrate make 'snippet.el' into a new package. The person of (1) and (2) can be the same. > it motivates someone to pick up the maintenance of the existing > > Yasnippet. > > Due to a sudden increase in free time available to me, I might consider > this. > Great, if you're serious about it drop me a line stating more or less what your plan is. I don't know if you've read the code: it's not exactly a work of art (at least my parts aren't) :-) If you'd prefer a more palatable challenge, you could opt to simply develop the somewhat nicer 'snippet.el'. It'd be fine to create your own repo to host and develop it (say in that shiny SourceHut account where we discussed a bug the other day). Jo=C3=A3o PS: in the meantime, it seems that Dmitry suggested what seems like a reasonable way to address your request. --0000000000004af3ef05e055fd33 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, May 31, 2022, 17:42 Philip Kaludercic= <philipk@posteo= .net> wrote:

To be specific, my issue was mentioned here: https://github.com/joaotavora/yasnippe= t/issues/1121 ("Avoid
false-positives when expanding snippets").=C2=A0 In my case, I have ma= naged
to circumvent the issue by unbinding the tab key and relying in
hippie-expand, but the solution is not elegant and I would have
appreciated a discussion on the issue tracker.
=

Does it really matter where t= he discussion happens? The problem
here is not = the place, it's the unavailability of brain-hours to dedicate
to your request.

The point was not to say that yasnippet has been abandoned, just to give an example where the liveliness of development could be questioned.

You don&= #39;t have to sugar-coat it. Yasnippet's bug reports have gone unanswer= ed
at least for a year. They don't make it = into my inbox, I'm not the maintainer
anymo= re. Noam did a thorough and excellent job while he was maintaining it,
=
he's not available anymore. It's de facto u= nmaintained, though rather stable
in its intend= ed use case.=C2=A0 Of course Emacs is gigantic and everyone wants
everything, and so it might not be doing what you want.= =C2=A0 I understand that.

In that sense, it'd be nice if yasnippet wasn= 't' the monolithic package it is,
and &= #39;snippet.el' is a step in that direction.=C2=A0 Then you could perha= ps opt out
(or in) to the multi-file, keybindin= g, abbrev-like functionality of yasnippet.el.=C2=A0
Or simply compose 'snippet.el' bare-bones expansion/navigation= with
whatever other productivity tool where yo= u think=C2=A0 snippets make sense.
Eglot is one= of those tools and it works well with yasnippet today.=C2=A0 I'd love = to
make it depend on simply 'snippet.el'.

> Is it just the general idea of abandonment of the fact that people'= ;s
> issue reports go unanswered?=C2=A0 If the latter, then I think archivi= ng to
> the repo would make sense.=C2=A0 No more issue reports would come in a= nd
> one could advertise the Emacs bug tracker.=C2=A0 Would that improve th= ings?

I guess, but I think it would be preferable to call for someone to fork
the package instead of shifting the burden of maintenance onto the emacs bug tracker.

Again, i don't quite understand how that magically solves t= he root problem
You're free to fork when you= want, of course, but that normally happens
whe= n you want to take the software in a new irreconcilable new direction.
Currently, yasnippet just needs = (1) a maintainer that understands the
current f= unctionality and "protects" it, fixing bugs, not introducing new = ones.
New features are probably not a great idea. (2= ) someone to develop 'snippet.el'
into = production-ready state and make 'yasnippet.el' depend on it, then m= ay
integrate make 'snippet.el' into a n= ew package. The person of (1) and (2) can
be th= e same.

> it motivates someone to pick up the maintenance of the existing
> Yasnippet.

Due to a sudden increase in free time available to me, I might consider
this.

Great, if you're serious abou= t it drop me a line stating more or less what
your plan is. I don= 't know if you've read the code: it's not exactly a work
of art (at least my parts aren't) :-) If you'd prefer a mo= re palatable challenge,
you could opt to simply develop the = somewhat nicer 'snippet.el'.=C2=A0 It'd be fine
= to create your own repo to host and develop it (say in that shiny SourceHut=
account where we discussed a bug the other day).

Jo=C3=A3o

PS: in the meantime, it = seems that Dmitry suggested what seems like a
reasonable way= to address your request.


--0000000000004af3ef05e055fd33--