melpa/melpa

[pr-open]: Add recipe for nonogram

tanrax — Wed, 09 Sep 2026 06:55:25 +0000

### Brief summary of what the package does

nonogram is a player for nonogram puzzles (also known as picross, griddlers or hanjie) inside Emacs. Fill the grid so each row and column matches its clue numbers and a hidden picture appears. The whole board, clue numbers included, is drawn with SVG on a solid background so it stays legible under any theme. It ships 33 bundled puzzles ordered from easiest to hardest, and can download and update more from a remote source.

### Direct link to the package repository

https://git.andros.dev/andros/nonogram.el

### Your association with the package

I am the author and maintainer.

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for el remoto

agzam — Wed, 09 Sep 2026 03:56:10 +0000

### Brief summary of what the package does

Browse any GitHub repository in Emacs as if it were cloned locally, without cloning it. It registers a virtual filesystem through `file-name-handler-alist` that turns ordinary Emacs file operations into GitHub API calls via `ghub`, so `find-file`, `dired`, tab completion and the rest of the standard file tooling work against a remote repo. Read-only. Issues and pull requests are browsable the same way, and optional Embark integration adds actions for the web and clone URLs.

### Direct link to the package repository

https://github.com/agzam/remoto.el

### Your association with the package

Author and maintainer.

### Relevant communications with the upstream package maintainer

**None needed.**

This is a resubmission of #9978, which I withdrew in May because I wanted to redesign the package rather than have you review a moving target. That redesign is done: the lookup architecture was reworked, issue and PR browsing was added, and so was the optional Embark layer. All the feedback from the first review is in: the `dired-get-filename` declaration, the double negations melpazoid reported, the checkdoc quoting, and `:fetcher` before `:repo` in the recipe. @riscy said at the time to open a new pull request rather than ask for a reopen.

Two things melpazoid still reports on the current tip, both deliberate:

- `Loading a package should rarely add hooks` (three) and `Avoid top-level advice or ensure you support (unload-feature) support` (one). The file-name handler, the hooks and the advice are what the package is; there is nothing to defer them behind. `remoto-unload-function` removes every one of them, and a test covers that.
- The GitHub release tag trails `Version:` by one patch. I will tag once this settles.

### Checklist

- [X] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [X] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [X] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [X] The package has been maintained in a public repository for 1 month or more
- [X] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [X] My elisp byte-compiles cleanly
- [X] I've used `M-x checkdoc` to check the package's documentation strings
- [X] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

One note on package-lint. Every `(any ...)` in an `rx` form is reported as a call to the function Emacs 31.1 added under that name, since package-lint 20260903 regenerated its stdlib data. The sources now use `in`, the `rx` synonym, so the run is clean, but the false positive will hit other packages using `rx`.

[pr-open]: Add recipe for amber-mode

GeorgGD — Tue, 08 Sep 2026 17:50:42 +0000

### Brief summary of what the package does

The package adds syntax highlighting and indentation rules for a programming language called amber-lang.

### Direct link to the package repository

https://codeberg.org/GeorgGD/amber-mode

### Your association with the package

I am the author and maintainer.

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for single-window

jamescherti — Tue, 08 Sep 2026 14:29:16 +0000

### Brief summary of what the package does

The single-window package forces Emacs to open buffers in the current active window.

It keeps your carefully arranged layouts intact, reduces visual clutter, and provides a much more predictable workflow. It handles edge cases by configuring modes like org-mode (src blocks and agenda) to respect the current window.

### Direct link to the package repository

https://github.com/jamescherti/single-window.el

### Your association with the package

Maintainer

### Relevant communications with the upstream package maintainer

**None needed**

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for preview-tab

ismd — Tue, 08 Sep 2026 11:48:56 +0000

### Brief summary of what the package does

VS Code's preview tab, for Emacs

### Direct link to the package repository

https://github.com/ismd/preview-tab.el

### Your association with the package

Maintainer

### Relevant communications with the upstream package maintainer

None needed

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [] The package has been maintained in a public repository for 1 month or more
- [] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [] My elisp byte-compiles cleanly
- [] I've used `M-x checkdoc` to check the package's documentation strings
- [] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for git-modeline

djangoliv — Mon, 07 Sep 2026 14:17:06 +0000

### Brief summary of what the package does

`git-modeline` is a global minor mode that prepends a colored mark to the
mode line of every buffer visiting a file inside a git repository. The color
gives the file's git status at a glance: up to date, modified, staged, added,
deleted or untracked. In particular it tells *staged* from *unstaged*
changes, which the built-in `vc-mode` indicator does not.

The mark is refreshed when a file is visited, saved or reverted, and changes
made outside Emacs are picked up automatically: a file-notification watch on
each repository's git directory catches a `git add`, `git reset` or commit run
from a terminal, and `magit-post-refresh-hook` catches the same from Magit.

Rendering is customizable through `git-modeline-decoration`: a large or small
XPM dot, a plain or colored status letter, or any function of your own. Each
state has its own face, so themes can restyle it, and on a terminal the dot
falls back to a colored letter automatically.

### Direct link to the package repository

https://github.com/djangoliv/git-modeline

### Your association with the package

I am the author and maintainer.

### Relevant communications with the upstream package maintainer

**None needed**, I maintain the package myself.

For transparency: the status-collection code originally derives from
[git-emacs](https://github.com/tsgates/git-emacs), which is GPLv3 like this
package. The attribution is kept in the header copyright line and in the
Commentary section.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for latex-to-svg-frontend

alberti42 — Mon, 07 Sep 2026 09:05:06 +0000

**AI disclaimer:** This PR was composed by me, aided by Opus 5.

### Brief summary of what the package does

`latex-to-svg-frontend` renders LaTeX math in a buffer as SVG images overlaid on the source, which stays in place so copy and save round-trip renderable LaTeX. It handles math detection, overlay lifecycle, equation numbering, `\ref` / `\eqref` resolution, reveal-on-cursor, and refreshing on theme and font changes. It is markup-agnostic: it never parses a specific markup itself, but asks the buffer's adaptor (two other "thin" packages, which are hosted in the same GitHub repo and which will be submitted as MELPA recipes in the future; more on this later) for the delimiters and the regions to skip.

The engine compiles each equation once and caches an SVG that is independent of color and size; a theme switch re-tints and a font change rescales straight from the cache. This ensures a very fast refresh of the equations on the buffer, without lengthy LaTeX recompilation when the theme or font size has changed.

### Short description on how it relates to other packages in MELPA

This is the frontend core of the latex-to-svg family whose engine, [`latex-to-svg-backend`](https://melpa.org/#/latex-to-svg-backend), you reviewed and merged in [#10152](https://github.com/melpa/melpa/pull/10152); this front-end package is different from [`agent-shell-math-renderer`](https://melpa.org/#/agent-shell-math-renderer), which was developed as an extension to [`agent-shell`](https://github.com/xenodium/agent-shell) and which you reviewed and merged in [#10198](https://github.com/melpa/melpa/pull/10198).

### Direct link to the package repository

https://github.com/alberti42/latex-to-svg

### Your association with the package

Author and maintainer.

### Relevant communications with the upstream package maintainer

**None needed.** The package uses only public Emacs API.

### Two more recipes to follow

The same repository holds two thin mode adaptors, `latex-to-svg-for-org` and `latex-to-svg-for-markdown`, which supply this core with a buffer's math delimiters and the regions to skip (source blocks, code fences) and turn it on. Since the math delimiters and rules for what needs to be skipped (e.g., comment regions) depend on the mode (Org, Markdown, etc.), I decided to split responsibilities between the core `latex-to-svg-frontend` and the mode-specific adaptors, without trying to create a universal front-end that aims at fitting to any kind of mode.

I am submitting this one first and will open pull requests for the adaptors once the core is merged, per `CONTRIBUTING.org`.

**If you want to see it working**, note that this package on its own renders nothing: it is the markup-agnostic core, and an adaptor is what tells it where the math is and turns it on. So a live test needs one adaptor from the same repository alongside it. Independently of the package manager:

```elisp
;; latex-to-svg-backend comes from MELPA; latex and dvisvgm must be on exec-path
(add-to-list 'load-path "/path/to/clone/of/latex-to-svg")
(require 'latex-to-svg-for-org) ; or latex-to-svg-for-markdown
(add-hook 'org-mode-hook #'latex-to-svg-for-org-mode)
```

Then open an Org file with `$x^2$` or a `\begin{equation}` block. The README shows the same with `straight`, `elpaca` and `package-vc-install`.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses) (GPL-3.0-or-later)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more (public since 2026-08-01)
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

melpazoid is clean, and `CHANNEL=stable` detects the current release, 0.15.2.

The `ignore-errors` pattern you flagged in #10152 is gone here too.

[pr-open]: Add recipe for donkey

YardQuit — Mon, 07 Sep 2026 08:35:30 +0000

### Brief summary of what the package does

An opinionated modal editing layer for Emacs in a single file. It adds a Normal state entered with `C-g`, with vi-style motions and counts, text-object marks (word, symbol, sentence, paragraph, delimiter pairs, balanced expressions), a "mark run" mode, line banking for non-contiguous selections, rectangles, wrapping, undo/redo and an in-package tutor (`M-x donkey-tutor`). It leans on native Emacs commands wherever possible and adds custom ones only where the behavior must differ. Optional Smartparens integration.

### Direct link to the package repository

https://github.com/YardQuit/donkey

### Your association with the package

Author and maintainer.

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

Notes: GPL-3.0 with a LICENSE file GitHub detects. Public since the 1.0.0 release on 2026-07-21; current release 1.7.1, tagged, and `CHANNEL=stable make recipes/donkey` picks the tag up as 1.7.1. Byte-compiled with warnings as errors, checkdoc and package-lint (2026-09-03) clean; CI runs the test suite on Emacs 29.1, 30.1 and 31.1.

[pr-open]: Add recipe for surveyor

mrcnski — Sun, 06 Sep 2026 15:11:54 +0000

### Brief summary of what the package does

A package to generate diagrams of code.

Uses the configured LLM through [gptel](https://github.com/karthink/gptel) and shows the result inline in an `image-mode` buffer. Supports flowcharts, sequence diagrams and class diagrams at two abstraction levels and renders through various pluggable engines.

`M-x surveyor` opens a transient menu where various parameters can be easily selected.

### Direct link to the package repository

https://github.com/mrcnski/surveyor.el

### Your association with the package

I am the author and maintainer.

### Relevant communications with the upstream package maintainer

None needed (I am upstream).

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses) (GPL-3.0-or-later)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more (public since 2026-07-22)
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback (clean)
- [x] My elisp byte-compiles cleanly (no warnings with `byte-compile-error-on-warn`)
- [x] I've used `M-x checkdoc` to check the package's documentation strings (clean)
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe) (`make recipes/surveyor` builds `surveyor-20260817.2132`; `CHANNEL=stable make recipes/surveyor` picks up the `v0.1.0` tag as `surveyor-0.1.0`; the built tar installs with `package-install-file` in a clean `emacs -Q` with gptel pulled from MELPA, and `surveyor` is autoloaded)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

[pr-open]: Return kostafey's repos to github

kostafey — Sun, 06 Sep 2026 01:21:48 +0000

[pr-open]: Add recipe for metropolis-light-theme

bitorhugo — Sun, 06 Sep 2026 01:11:27 +0000

### Brief summary of what the package does
A light theme based on the Metropolis Beamer color palette.

### Direct link to the package repository

https://github.com/bitorhugo/metropolis-light-theme

### Your association with the package

Maintainer

### Relevant communications with the upstream package maintainer

**None needed**

### Checklist

- [X] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [X] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [X] The package has been maintained in a public repository for 1 month or more
- [X] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [X] My elisp byte-compiles cleanly
- [X] I've used `M-x checkdoc` to check the package's documentation strings
- [X] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for org-roam-gt

dmgerman — Sun, 06 Sep 2026 00:05:51 +0000

### Brief summary of what the package does

org-roam-gt enhances org-roam with performance improvements and better capture templates

### Direct link to the package repository

https://github.com/dmgerman/org-roam-gt

### Your association with the package

I am the author and maintainer.

### Relevant communications with the upstream package maintainer

**None needed** I maintain the package myself.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Update upstreams for term-cmd and term-alert

calliecameron — Sat, 05 Sep 2026 13:02:27 +0000

[pr-open]: Add mode-line-path

arthurgleckler — Sat, 05 Sep 2026 00:53:57 +0000

### Brief summary of what the package does

Display an abbreviated file path in the GNU Emacs mode line. Shorten long paths using the values of short environment variable names (three characters or fewer) as prefixes. If a path is still too long, truncate it with an ellipsis.

I'm re-posting this pull request, which was originally [10116](https://github.com/melpa/melpa/pull/10116), because the project has now been maintained in a public repository for more than one month. That was the only thing missing originally.

### Direct link to the package repository

https://github.com/arthurgleckler/mode-line-path

### Your association with the package

I wrote this in 2013, and have used it every day since. Being able to see an abbreviated version of the full path of each buffer in the mode line is great for context. Preparing this package for MELPA, I cleaned it up extensively, hoping to make it useful to others. I added caching, customizations, and tests. (Even without caching, it has always been fast, but I added it in case some users have enormous numbers of environment variables, for example. The one-second cache TTL means that caching isn't noticeable.)

### Relevant communications with the upstream package maintainer

**None needed**

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for modern-tab

MArpogaus — Fri, 04 Sep 2026 22:34:08 +0000

### Brief summary of what the package does

modern-tab gives the two rows of tabs Emacs has the look of the editors
people come here from: `modern-tab-bar-mode` dresses the tab bar, one
tab per tab group, and `modern-tab-line-mode` the tab line, one tab per
buffer of a window. A coloured indicator beside the selected tab, an
icon on every tab (from nerd-icons where it is installed, plain
characters otherwise), buttons of one glyph family, a tab line that
hides itself where a window shows one buffer, and every variable a mode
borrows from `tab-bar` and `tab-line` given back when it is turned off.
The two modes are independent.

The package is `modern-tab`, after its main file and the prefix of every
symbol; the repository is `modern-tabs`, after the two rows it dresses.
The tarball holds `modern-tab.el`, `modern-tab-bar.el` and
`modern-tab-line.el`.

### Direct link to the package repository

https://github.com/MArpogaus/modern-tabs

### Your association with the package

I am the author and the maintainer.

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [ ] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

Notes on the boxes above:

The repository itself is new: the code was split out of
[auto-tab-groups](https://github.com/MArpogaus/auto-tab-groups) (#10157),
where it lived as `auto-tab-groups-eyecandy.el` since 2024, and out of my
configuration, on 2026-09-03. If a month in its own repository is what
the rule means, I am happy for this PR to wait until then.

`make` in the repository runs byte-compilation with warnings as errors,
package-lint with `package-lint-main-file` set to `modern-tab.el`,
relint and 48 ERT tests; CI runs the same on Emacs 29.1, 30.1, 30.2,
31.1 and snapshot, plus melpazoid and the checkdoc and indentation
hooks on every push. The repository is at version 1.0 (tag `v1.0`). I
built the recipe in a fresh melpa checkout with `make recipes/modern-tab`
and installed it with `make sandbox INSTALL=modern-tab`.

[pr-open]: Add recipe for api-credit

OverbearingPearl — Fri, 04 Sep 2026 15:56:14 +0000

### Brief summary of what the package does

Display AI API account balances in the Emacs mode line. This package
is deliberately provider-agnostic: adding support for a new AI API is
usually just a few lines added to `api-credit--providers'.

### Direct link to the package repository

https://github.com/OverbearingPearl/api-credit

### Your association with the package

I am the author and maintainer.

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Remove recipe magik-company, deprecated by upstream author

reinierkof — Fri, 04 Sep 2026 10:48:17 +0000

### Reason

Magik-company was an external package to complement magik-mode.

A proper completion framework is now integrated into magik-mode, making this package redundant.

### Brief summary of what the package does

Completion package

### Direct link to the package repository

https://github.com/reinierkof/magik-company

### Your association with the package

I am the author.

[pr-open]: Use default value for package-build-build-function

tttuuu888 — Thu, 03 Sep 2026 17:32:51 +0000

Hi, this PR fixes #10200.
Package-Build 5.0.2 removed `package-build--build-multi-file-package` and now defaults to `package-build--build-package`.
So I dropped the two `setq` lines from the Makefile and verified that a package builds successfully.

Thank you.

[pr-open]: Rename pi-coding-agent -> pilish

dnouri — Thu, 03 Sep 2026 15:11:08 +0000

# Rename pi-coding-agent -> pilish

Sorry for the shuffle around this recipe. The repo was renamed to `piem` at first (#10197, closed after the clash with Kyle Meyer's `piem`), rolled back, and is now https://github.com/dnouri/pilish

I checked `pilish` against MELPA, GNU ELPA, NonGNU ELPA, and emacsmirror — the name is free.

```diff
-(pi-coding-agent :fetcher github :repo "dnouri/piem")
+(pilish :fetcher github :repo "dnouri/pilish" :old-names (pi-coding-agent))
```

`:old-names` keeps the download counts and shows "Renamed from: pi-coding-agent" on the site.

For users it's a clean break: install `pilish`, `M-x package-delete RET pi-coding-agent`, then rename `pi-coding-agent` to `pilish` in their init. The README covers the details.

### Brief summary of what the package does

Emacs frontend for the pi coding agent (https://pi.dev): a two-window UI with a rendered-Markdown chat buffer and a separate prompt buffer, plus disk-backed session and conversation-tree browsers.

### Direct link to the package repository

https://github.com/dnouri/pilish

### Your association with the package

Maintainer.

### Relevant communications with the upstream package maintainer

None needed.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

[pr-open]: Add recipe for agent-shell-math-renderer

alberti42 — Thu, 03 Sep 2026 12:27:48 +0000

**AI disclaimer:** This PR was prepared with the help of Opus 5. I reviewed the submitted material and tweaked the PR description.

### Brief summary of what the package does

This is one of the user-facing packages that accompany [`latex-to-svg-backend`](https://melpa.org/#/latex-to-svg-backend), the rendering engine you reviewed and merged in [#10152](https://github.com/melpa/melpa/pull/10152). The engine does the typesetting; this package finds the equations and places the images.

It renders LaTeX math in [`agent-shell`](https://github.com/xenodium/agent-shell)'s streamed markdown output. Display equations (`$$…$$`, `\[…\]`, ```` ```math ```` fences) and inline math (`$…$`) are shown as theme-matched SVG images overlaid on the source, which stays in the buffer so copy and save round-trip renderable LaTeX. It plugs in through agent-shell's public `agent-shell-markdown-render-functions` extension point: no patching, no advice.

### Direct link to the package repository

https://github.com/alberti42/agent-shell-math-renderer

### Your association with the package

Author and maintainer.

### Relevant communications with the upstream package maintainer

**None needed** for `package.el` compatibility: the integration uses only agent-shell's public hook.

One naming note, as in #10152: `agent-shell-` is the de-facto pattern agent-shell's maintainer (Álvaro Ramírez, xenodium) uses for third-party extensions, and this package is listed in agent-shell's own ["Related projects"](https://github.com/xenodium/agent-shell#related-projects) section, where its addition was welcomed. It is an add-on, not a claim on the namespace.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses) (GPL-3.0-or-later)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more (public since 2026-07-02)
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

### On the review of the backend companion package #10152

Two things carried over from your review of the backend recipe:

- The `ignore-errors` pattern you flagged in the backend package is gone here too. This package had one occurrence; it now names the condition it recovers from and reports it once per buffer rather than swallowing it.
- melpazoid is clean.

Release v0.9.1 is current with the code and the `Version:` header, and `MELPA_CHANNEL=stable make recipes/agent-shell-math-renderer` detects 0.9.1.

[pr-open]: Rename pi-coding-agent to piem

dnouri — Wed, 02 Sep 2026 19:07:52 +0000

pi-coding-agent has been renamed to **piem**.

When the package was added in #9757, "pi.el" alone was too ambiguous, and so I chose "pi-coding-agent". In hindsight that wasn't a great name after all. For one, it clashes with upstream which contains a package called "pi-coding-agent" [itself](https://github.com/earendil-works/pi/tree/main/packages/coding-agent).

There have also been new Emacs support packages since, for example the vterm frontend in #10055, so "pi-coding-agent" seems like a poor fit today. It's why I did the rename to the less awkward and more unique "piem", which stands for "Pi for Emacs"; also piems are [a fun concept on their own](https://maths-from-the-past.org/pi-piem-and-piphilology-2/).

The package side of the rename is complete:

- `v3.0.0` is tagged and matches the `Version` header (per the stable-channel requirement, as in #9539)
- All old entry points keep working as deprecated aliases (scheduled for removal in 4.0), and old-name `setq`/`customize` settings migrate automatically on load
- The README has an "Upgrading from pi-coding-agent" section, and piem itself warns users to `M-x package-delete` the old package if it's still installed
- Development was assisted by the `pi` coding agent, recorded via `Assisted-by:` lines in `piem.el`

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and if so, I've added an `Assisted-by:` line as described in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#attribution-for-ai-generated-code)
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

Recipe change: the recipe file moves from `recipes/pi-coding-agent` to `recipes/piem`:

```elisp
(piem :fetcher github :repo "dnouri/piem"
:old-names (pi-coding-agent))
```

Thanks!

[pr-open]: Add recipe for journalctl

WJCFerguson — Tue, 01 Sep 2026 22:49:46 +0000

### Brief summary of what the package does

Major mode for viewing and `--follow`ing journald logs via `journalctl` on Linux systems (including remote hosts over TRAMP). It parses `--output json` records, giving:

- Formatted, prioritized-highlighted output with wrapped messages
- Multiple simultaneous `journalctl` queries interleaved and de-duplicated in timestamp order into one buffer — e.g. a broad `--priority warning` query alongside a narrow `--grep` query
- Region-based drill-down: an active region yields a ready-made `--since`/`--until` string for follow-up queries
- Timestamps rendered in the queried system's timezone, so they remain valid in further `--since`/`--until` arguments
- Jump-to-source (`M-.`) when records carry `CODE_FILE`/`CODE_LINE`
- Buffer capped at `journalctl-buffer-maximum-lines` so a long `--follow` cannot grow without bound

##### Direct link to the package repository

https://github.com/WJCFerguson/journalctl

##### Your association with the package

Author and maintainer.

##### Relationship to the existing `journalctl-mode` package (raising this upfront)

MELPA already hosts [`journalctl-mode`](https://github.com/SebastianMeisel/journalctl-mode), which is unrelated and takes a different approach: it provides a query-building UI with synchronous chunked loading, while this package interleaves multiple asynchronous JSON queries. The naming overlap is unfortunate history, and both packages currently define the commands `journalctl` and `journalctl-mode`, so they cannot be co-installed — this package's README documents the conflict prominently and tells users to install only one. Let me know if the recipe name is too close or the symbol clash disqualifying.

##### Checklist

- [x] The package is released under a GPL-compatible license (GPLv3; `COPYING` included)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] `package-lint` reports no issues
- [x] Byte-compiles cleanly on Emacs 29.1 (the declared minimum)
- [x] `checkdoc` reports no issues
- [x] ERT test suite included upstream (`journalctl-tests.el`, excluded from the package by the default files spec)
- [x] I am the upstream maintainer

**Recipe** (`recipes/journalctl`):
```elisp
(journalctl :fetcher github :repo "WJCFerguson/journalctl")
```

[pr-open]: Add recipe for evil-twin

teeann — Mon, 31 Aug 2026 22:54:36 +0000

### Brief summary of what the package does

`evil-twin` makes [key-chord](https://github.com/emacsorphanage/key-chord) work correctly with [evil](https://github.com/emacs-evil/evil): two-key chords bound directly into evil's per-state keymaps (normal/motion by default), with `key-chord-mode` left on permanently. This avoids the common-but-fragile approach of toggling the global `key-chord-mode` from evil state-change hooks, and adds zero latency in states (e.g. insert) where no chord is bound.

### Direct link to the package repository

https://github.com/teeann/evil-twin

### Your association with the package

I am the author and maintainer.

### Relevant communications with the upstream package maintainer

N/A — I am the upstream maintainer.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html) (GPL-3.0-or-later; `LICENSE` included).
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org).
- [x] I've used the latest version of `package-lint` to check for packaging issues, and addressed its feedback.
- [x] My elisp byte-compiles cleanly.
- [x] `M-x checkdoc` is happy with my docstrings.
- [x] I've built the package (`make recipes/evil-twin`) and it builds without errors; the generated metadata (summary, `Package-Requires`, URL) is correct.

[pr-open]: Update recipe for fzf-native to include source build files

dangduc — Mon, 31 Aug 2026 03:00:42 +0000

### Brief summary of what the package does

fzf-native provides fuzzy matching and highlighting through an Emacs dynamic module.

This recipe update ships the vendored utf8proc tree, license files, include fragments, and platform linker/export inputs required to rebuild the module locally. It also excludes test files and the test-only module initialization probe from installed archives.

### Direct link to the package repository

https://github.com/dangduc/fzf-native

### Your association with the package

I am the maintainer.

### Relevant communications with the upstream package maintainer

Change in recipe addresses the local binary build failure documented in https://github.com/dangduc/fzf-native/issues/44.

The companion source compliance audit is https://github.com/dangduc/fzf-native/pull/45.

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [x] I've read [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org)
- [x] LLMs were used to generate some of the code, and `Assisted-by: Codex:gpt-5` is recorded in the source audit and commit trailers
- [x] The package has been maintained in a public repository for 1 month or more
- [x] I've used the latest version of [package-lint](https://github.com/purcell/package-lint) to check for packaging issues, and addressed its feedback in the companion source branch
- [x] My elisp byte-compiles cleanly
- [x] I've used `M-x checkdoc` to check the package's documentation strings
- [x] I've built and installed the package using the instructions in [CONTRIBUTING.org](https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#test-your-recipe)

Validation covered rolling and stable recipe builds, archive-content checks, isolated installation, loading the bundled module, and compiling/loading a module from the installed source archive.

`CONTRIBUTING.org` currently documents `MELPA_CHANNEL=stable`, while the current Makefile reads `CHANNEL`; stable validation therefore used `make CHANNEL=stable recipes/fzf-native`.

Assisted-by: Codex:gpt-5

[pr-open]: Remove recipe for smilefjes.el

themkat — Sun, 30 Aug 2026 20:05:31 +0000

smilefjes.el no longer works, as the API it used is decommissioned. Sorry for not sending in this PR earlier; I was hoping that we would get a new candidate API. Think the best course of action is to remove it, so people don't download a non-working package.

I'm the maintainer and owner.

Sorry again, I have postponed this for far too long....

[pr-open]: Updated branch in ox-leanpub recipe

zzamboni — Sun, 30 Aug 2026 16:31:38 +0000

Was using the default branch, I renamed the default branch from "master" to "main" recently and the changes are not being picked up, so adding a specific branch name in the recipe.