1. 26
    1. 10

      Indeed it is. I hoped that ‘emacs’ tag would make that clear enough.

      1. 9

        I often don’t notice tags when scanning the title list.

        I think “Emacs Helm development is now stalled” would be clearer.

    2. 21

      I recently discovered and appreciated expand-region.el’s “maintenance warning”:

      I use this package every day, and have been doing so for years. It just works. At least, it works for all my use cases. And if it breaks somehow, I fix it.

      However, it has become painfully clear to me that I don’t have time to fix problems I don’t have. It’s been years since I could keep pace with the issues and pull requests. Whenever I try, I keep getting feedback that my fix isn’t good enough by some standard I don’t particularly care about.

      So, I have closed the issue tracker and the pull requests. I hope you can happily use this package, just like I do. If it doesn’t work for you, then I’m sorry. Thankfully Emacs is infinitely malleable, you can probably fix it yourself.

      TLDR: I am still maintaining this package, but I am no longer crowdsourcing a list of issues.

      1. 4

        At least, it works for all my use cases

        incidentally, there was one thing in expand-region.el that bugged me for quite some time and yesterday I finally sat down and refused to give myself a break until I fixed it.

        ;; Expand region for whatever reason ignores lines when expanding, it should
        ;; start expanding from a word, then to a line, then to a paragraph, and so
        ;; on. But default implementation ignores the line expansion.
        (defun er/mark-line ()
          "Marks entire 'logical' line."
          (set-mark (point))
           er/mark-method-call er/mark-inside-quotes
           er/mark-outside-quotes er/mark-inside-pairs
           er/mark-outside-pairs er/mark-comment er/mark-url
           er/mark-email er/mark-defun))
      2. 19

        This interview with the (former) Helm maintainer is really good. Turns out he’s a alpine guide who never programmed for a living.


        1. 7

          I’m not terribly surprised; my most recent bug report was met with a fairly cranky response, which felt like burnout. I can tell that the maintainer did not like that his work was being vended via Spacemacs, which seemed to be a source of great frustration for him, since he didn’t use it but bug reports would come from people who did.

          1. 3

            I wonder why they didn’t archive the repo?

            But unrelated, this is one of the problems when packages are maintained externally. Just because development has stalled, doesn’t mean the package should die. Hopefully, the recent discussions about non-GNU ELPA (Emacs Lisp Package Archive) will help alleviate issues like these.

            1. 2

              Or at least update the README or FAQ. I can’t count the number of times that some very important update was buried in an issue of a project, only to be found after fighting with it for an hour.

            2. 2

              I flagged this post mainly because there is nothing in it, except a curt announcement. Nothing to learn from. I liked helm, it’s pretty fast and well customizable.

              1. 14

                Well you might have learned that the package you liked ceased the development.

                1. 1

                  True, but it’s still a news item that fits a tweet. When I said “Nothing to learn from”, I meant that I could not learn why it had happened to the project, a lesson learned so one could not repeat it, nor were there any next steps, really, nothing.

                  Software projects come and go, that’s a sad reality. Many of mine favorite projects have stalled or ceased to exist. Some of them came back, after community could be formed around it (for example, zprezto).

              2. 1

                Well this was a confusing post.

                1. 1

                  Does Emacs maintain backwards compatibility with old package code?

                  1. 3

                    Emacs is extremely democratic and egalitarian, self-regulating ecosystem. If something breaks, there’s always someone who’d fix it. Good ideas rarely die here, they thrive and evolve. And to answer your question: yes, Emacsen are very strict about maintaining backwards compatibility. If added feature to emacs-core makes it stop working with some popular package, there’s always a discussion in emacs-dev mailing list, and such issues quickly get addressed.