home.social

#elpa — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #elpa, aggregated by home.social.

fetched live
  1. For anyone who maintains Emacs packages on ELPA, I would be interested in feedback to this thread on emacs-devel: lists.gnu.org/archive/html/ema

    The basic question is what the preferred approach would be to annotate what parts of a changelog file pertain to a specific/current release, so that we could extract this information and use it in say the Atom feed or a package, or in the future in package-specific bots on the Fediverse.

    Comments are welcome here, on emacs-devel or privately.

    #elpa #emacs

  2. For anyone who maintains Emacs packages on ELPA, I would be interested in feedback to this thread on emacs-devel: lists.gnu.org/archive/html/ema

    The basic question is what the preferred approach would be to annotate what parts of a changelog file pertain to a specific/current release, so that we could extract this information and use it in say the Atom feed or a package, or in the future in package-specific bots on the Fediverse.

    Comments are welcome here, on emacs-devel or privately.

    #elpa #emacs

  3. I tagged a bunch of #emacs package releases:

    - Cape 2.8: Better cape-dabbrev case folding and fixes to cape-capf-super
    - Corfu 2.12, Osm 2.5: Improvements to mouse support
    - Elfeed 4.1.1: Much more robust database loading
    - Jinx 2.9: New command jinx-remove-word

    They will appear soon on the stable #elpa and #melpa channels.

  4. I tagged a bunch of #emacs package releases:

    - Cape 2.8: Better cape-dabbrev case folding and fixes to cape-capf-super
    - Corfu 2.12, Osm 2.5: Improvements to mouse support
    - Elfeed 4.1.1: Much more robust database loading
    - Jinx 2.9: New command jinx-remove-word

    They will appear soon on the stable #elpa and #melpa channels.

  5. @projectgus I use package.el with package-review-policy=t such that I can inspect all diffs on upgrade. Furthermore I mirror all package versions with daily tags for potential analysis. github.com/emacs-elpa/mirror #emacs #elpa

  6. @projectgus I use package.el with package-review-policy=t such that I can inspect all diffs on upgrade. Furthermore I mirror all package versions with daily tags for potential analysis. github.com/emacs-elpa/mirror #emacs #elpa

  7. So glad that MELPA is getting a new versioning scheme, such that all ELPA snapshot archives become compatible. Snapshot package versions have the form release.0.date.count, starting with the version number of the last release.

    snapshots.melpa.org/
    releases.melpa.org/

    github.com/melpa/melpa/pull/10

    #emacs #melpa #elpa

    @tarsius @sanityinc

  8. So glad that MELPA is getting a new versioning scheme, such that all ELPA snapshot archives become compatible. Snapshot package versions have the form release.0.date.count, starting with the version number of the last release.

    snapshots.melpa.org/
    releases.melpa.org/

    github.com/melpa/melpa/pull/10

    #emacs #melpa #elpa

    @tarsius @sanityinc

  9. An ELPA traffic cadet is once again trying to make up rules which the ELPA maintainers have to follow, while not having contributed anything significant to Emacs or ELPA himself:

    lists.gnu.org/archive/html/ema

    Emacs and ELPA are under continuous pressure by some people with a political agenda. This makes it difficult to contribute there since the rules may change from one day to another.

    @pkal @tarsius

    #emacs #elpa

  10. An ELPA traffic cadet is once again trying to make up rules which the ELPA maintainers have to follow, while not having contributed anything significant to Emacs or ELPA himself:

    lists.gnu.org/archive/html/ema

    Emacs and ELPA are under continuous pressure by some people with a political agenda. This makes it difficult to contribute there since the rules may change from one day to another.

    @pkal @tarsius

    #emacs #elpa

  11. The entirety of ELPA + MELPA as mirror is only around 3.7G (2.2G gzipped). I had expected that a full Emacs installation would be larger. #emacs #elpa

  12. The entirety of ELPA + MELPA as mirror is only around 3.7G (2.2G gzipped). I had expected that a full Emacs installation would be larger. #emacs #elpa

  13. I just tagged stable versions of many of my Emacs packages, most of them with small bug fixes, and the upgrade to Compat 31. #emacs #elpa

  14. I just tagged stable versions of many of my Emacs packages, most of them with small bug fixes, and the upgrade to Compat 31. #emacs #elpa

  15. @pkal I like your new ELPA redesign - but may I suggest to keep the old colors? I like them, even if they are a bit strong, and I also find it important that the archive stays recognizable.

    - old: elpa.gnu.org/
    - new: pkal.sdf.org/gnu-elpa/

    #emacs #elpa

  16. @pkal I like your new ELPA redesign - but may I suggest to keep the old colors? I like them, even if they are a bit strong, and I also find it important that the archive stays recognizable.

    - old: elpa.gnu.org/
    - new: pkal.sdf.org/gnu-elpa/

    #emacs #elpa

  17. For anyone interested in publishing an Emacs package on GNU or NonGNU ELPA, we just added a page on how to do that and what to keep in mind: elpa.gnu.org/contributing.html

    If anything is not clear, please reach out! My hope is that this document can help clarify some of the misconceptions around ELPA and demystify the process.

    #emacs #elpa

  18. For anyone interested in publishing an Emacs package on GNU or NonGNU ELPA, we just added a page on how to do that and what to keep in mind: elpa.gnu.org/contributing.html

    If anything is not clear, please reach out! My hope is that this document can help clarify some of the misconceptions around ELPA and demystify the process.

    #emacs #elpa

  19. If you're facing weird effects or poor performance when working with #Emacs (or #orgmode) and you're having a customized setup:

    One thing that may solve some issues is removing your elpa/melpa packages and let it install from scratch.

    It might be a good idea not to mix up #melpa and #elpa packages as it might introduce broken dependencies with mismatching package versions.

    I've had my learning yesterday and it cost me and unfortunately another expert half of the day to find out about my mistake(s).

    Edit: I initiated a #WORG page for tips like that: orgmode.org/worg/org-performan

  20. If you're facing weird effects or poor performance when working with #Emacs (or #orgmode) and you're having a customized setup:

    One thing that may solve some issues is removing your elpa/melpa packages and let it install from scratch.

    It might be a good idea not to mix up #melpa and #elpa packages as it might introduce broken dependencies with mismatching package versions.

    I've had my learning yesterday and it cost me and unfortunately another expert half of the day to find out about my mistake(s).

    Edit: I initiated a #WORG page for tips like that: orgmode.org/worg/org-performan

  21. A proposal for reviewing Emacs package releases on ELPA: mail.gnu.org/archive/html/emac

    I would appreciate feedback, especially from people who have packages on {,Non}GNU ELPA. So if possible, please share the link on other channels.

    Edit: To be clear, I am not looking for reactions here or on other sites, but on the mailing list!

    #emacs #elpa

  22. A proposal for reviewing Emacs package releases on ELPA: mail.gnu.org/archive/html/emac

    I would appreciate feedback, especially from people who have packages on {,Non}GNU ELPA. So if possible, please share the link on other channels.

    Edit: To be clear, I am not looking for reactions here or on other sites, but on the mailing list!

    #emacs #elpa

  23. Still chugging along: two issues down and a few more to go before I'm ready to submit this for publishing as an #emacs package on #elpa.

    I'm very excited for that day! Can't wait to see my software be useful for others. And maybe, just maybe, receive some contributions.