melpa/melpa

[pr-open]: Add recipe for magit-nix3

akirak — Thu, 08 Oct 2026 12:00:46 +0000

### Brief summary of what the package does

Integrate Nix flake features with magit

### Direct link to the package repository

https://github.com/emacs-twist/nix3.el

### Your association with the package

I am 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)
- [x] I understand the package must have 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 lark

bbw9n — Wed, 07 Oct 2026 09:27:05 +0000

### Brief summary of what the package does

Running the [lark cli](https://github.com/larksuite/cli) in emacs with a common share context layer for your work

### Direct link to the package repository

https://github.com/bbw9n/lark.el

### Your association with the package

I'm the maintainer of this package

### 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] I understand the package must have 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 xdg-redirect

francisco-colaco — Sun, 04 Oct 2026 11:52:54 +0000

### Brief summary of what the package does

### Direct link to the package repository

https://github.com/your/awesome_package

### Your association with the package

### Relevant communications with the upstream package maintainer

### Checklist

- [x] The package is released under a [GPL-Compatible Free Software License](https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses)
- [ ] 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] I understand the package must have 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 bongo-cat-mode

luyangliuable — Sun, 04 Oct 2026 11:30:20 +0000

### Brief summary of what the package does

Displays a small animated Bongo Cat in the mode-line. When you type, only the cat in that Emacs window alternates paw frames and appears to beat on the keyboard; cats in other windows stay idle. A second mode, `bongo-cat-scroll-mode`, flattens the cat and slides it left and right along a track following the window's scroll position (`window-start`/`window-end`, like `%p`/`%P` and `sml-modeline`).

Similar existing package: `nyan-mode`. Differences: the animation is per-window and driven by typing in that window rather than a global loop, and it has a scroll-position tracker variant with a matching solid/faint rail drawn in the mode-line.

### Direct link to the package repository

https://github.com/luyangliuable/bongo-cat-model.el

### 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)
- [ ] 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] I understand the package must have 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-closed]: Add recipe for antigravity-cli-ide

iht — Sun, 04 Oct 2026 23:00:07 +0000

### Brief summary of what the package does

Native GNU Emacs IDE integration for the Google Antigravity CLI (`agy`) executable via the Model Context Protocol (MCP).

Unlike simple terminal wrappers, `antigravity-cli-ide` creates a bidirectional bridge connecting Antigravity directly to Emacs editor capabilities (LSP/xref, compiler diagnostics via Flymake/Flycheck, tree-sitter AST queries, and interactive Ediff comparisons) using a zero-dependency local TCP socket bridge.

Adapted from and inspired by `claude-code-ide.el` by Yoav Orot, redesigned with a pure TCP loopback bridge requiring zero external dependencies.

### Direct link to the package repository

https://github.com/iht/agy-cli-emacs

### Your association with the package

Author and maintainer

### Relevant communications with the upstream package maintainer

**None needed** (I am the package maintainer)

### 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] I understand the package must have 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 antigravity-cli-ide

iht — Sat, 03 Oct 2026 21:53:57 +0000

[pr-open]: Add recipe for markdown-ts-appear

Thysrael — Fri, 02 Oct 2026 20:30:53 +0000

### Brief summary of what the package does

`markdown-ts-appear` is a minor mode for Emacs 31.1+'s built-in `markdown-ts-mode`. It reveals the Markdown source of the smallest element at point and restores its rendered appearance when point leaves, without changing buffer text.

It includes configurable link icons, code fences, quote and callout rendering, width-aware tables using `markdown-table-wrap`, optional MathJax previews, and controls for insert-state-only source reveal with Evil or Meow. The source-reveal interaction is similar to `org-appear`, but targets the built-in Tree-sitter Markdown mode rather than Org. It extends `markdown-ts-mode` rather than replacing it or the separate `markdown-mode` package.

### Direct link to the package repository

https://github.com/Thysrael/markdown-ts-appear

Latest release: https://github.com/Thysrael/markdown-ts-appear/releases/tag/v0.2.3

### Your association with the package

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) (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 the source files include `Assisted-by:` attribution.
- [x] I understand the package must have been maintained in a public repository for 1 month or more. The repository has been public since September 2, 2026.
- [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 (CI installs it from MELPA).
- [x] My elisp byte-compiles cleanly.
- [x] I've used `M-x checkdoc` to check the package's documentation strings (also run in batch CI).
- [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

- [Passing upstream CI](https://github.com/Thysrael/markdown-ts-appear/actions/runs/36978381588): Emacs 31.1 and snapshot, pinned/latest Markdown grammars, real MathJax coverage on macOS, byte compilation, checkdoc, package-lint, and terminal regressions.
- 136 ERT tests passed locally.
- Built the recipe for MELPA and MELPA Stable; Stable correctly selects `0.2.3`.
- Installed the built Stable tarball with `package-install-file` in an isolated package directory, with `markdown-table-wrap`, and successfully loaded `markdown-ts-appear`.
- Local recipe builds used `CONFIG="(setq package-build-badge-data nil)"` because the local ImageMagick installation lacks the badge font. Package building and installation succeeded.

The default file selection includes only the three package libraries; tests, examples, and the README are not packaged. `markdown-table-wrap` is already in MELPA. MathJax is optional and is not a required dependency.

[pr-open]: Add recipe for devops

kpassapk — Thu, 01 Oct 2026 15:55:02 +0000

### Brief summary of what the package does

devops.el makes it easier to work with remote servers in org-babel. It uses server "named targets" defined at the top of an org file. When these server targets appear as heading tags, all source blocks under that heading run there. I have almost switched to it as my "shell": since I don't have to worry at the same time about what to run and where to run it, I can stay focused and be more productive.

devops.el also encourages using noweb and tangling to upload files to servers. Tangling follows the same named targets. The package can then help identify when the file contents has drifted between the local file and the server.

The package has been about 7 months in the making, and I am managing all
my server infrastructure with it.

### Direct link to the package repository

https://github.com/kpassapk/devops.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] I understand the package must have 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-closed]: Remove recipe for ivy-fuz

Silex — Wed, 30 Sep 2026 21:36:59 +0000

I'm the owner of [ivy-fuz.el](https://github.com/Silex/ivy-fuz.el).

It has had no changes since 2019. I no longer use ivy, and no package on MELPA depends on it. I plan to delete the repository once this recipe is removed, so the recipe would stop building.

[pr-open]: Remove recipe for ivy-fuz

Silex — Wed, 30 Sep 2026 12:49:37 +0000

[pr-open]: Add recipe for epher

upyesp — Wed, 30 Sep 2026 12:28:33 +0000

### Brief summary of what the package does

epher is the Emacs client of the epher calculator language. You write ordinary math with units that convert; every statement's answer appears inline next to its line as an inlay hint, and `C-c C-c` runs the whole script through the language server, with each graph written to an SVG file and opened in the system viewer.

One note up front: the package lives in a version-locked monorepo rather than a dedicated repository (ADR-0066: one calculator, one language server, one grammar, clients per editor). The `:files` spec serves the single `epher.el` and all clients share the same `v0.5.x` tags, so the per-package-version concern behind the dedicated-repo guideline is met by construction.

### Direct link to the package repository

https://github.com/upyesp/epher

### Your association with the package

I maintain epher upstream.

### Relevant communications with the upstream package maintainer

None needed, 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#GPLCompatibleLicents): MIT, full text at the repo root, SPDX notice in the header.
- [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): `epher.el` line 4 reads `;; Assisted-by: GLM (Z.ai)`
- [x] I understand the package must have 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: HEAD (0.26) today reports one deliberate warning, the `with-eval-after-load` that registers our client with optional lsp-mode, the pattern lsp-mode's own docs prescribe.
- [x] My elisp byte-compiles cleanly (Emacs 28.2 and 30.2)
- [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-closed]: Add recipe for org-slideboard

vikasrawal — Sun, 04 Oct 2026 18:30:44 +0000

### Brief summary of what the package does

org-slideboard presents Org files as slides inside Emacs, aimed at files written for Beamer export. It shows Beamer columns side by side in separate windows and generates title and section pages. It fits text to the window, and lays out lists, tables (aligned to what is actually displayed), LaTeX equations(sized to the text) and Org macros for the slide. Source blocks can be shown as code, results, or both, side by side or top to bottom, also inside a Beamer column. `C-c C-c` updates the results, and editing a block shows it next to a running R (ESS) or Python REPL. The text stays live Org, so slides can be edited during the show.

Similar packages: org-tree-slide, org-present, epresent, dslide. It is derived from John Kitchin's org-show (part of scimax, not on MELPA), which was based onSacha Chua's presentation code. It differs mainly in following Beamer's layout
and in its handling of code and results.

### Direct link to the package repository
https://github.com/vikasrawal/org-slideboard

### Your association with the package
I am the author and maintainer. The package started from John Kitchin'sorg-show, which is credited in the file header and README.

### Relevant communications with the upstream package maintainer

**None needed**. I am the maintainer. org-show is part of scimax and was never packaged separately.

### Checklist

- [x] The package is released under a GPL-Compatible Free Software License
- [x] I've read 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
- [ ] I understand the package must have been maintained in a public repository for 1 month or more
- [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] 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

[pr-open]: Add recipe for org-slideboard

vikasrawal — Tue, 29 Sep 2026 18:39:04 +0000

[pr-closed]: Add recipe for latex-to-svg-for-latex

alberti42 — Sun, 04 Oct 2026 18:30:01 +0000

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

This is the third adaptor of the `latex-to-svg` front-end, after [`latex-to-svg-for-org`](https://melpa.org/#/latex-to-svg-for-org) ([#10234](https://github.com/melpa/melpa/pull/10234)) and [`latex-to-svg-for-markdown`](https://melpa.org/#/latex-to-svg-for-markdown) ([#10243](https://github.com/melpa/melpa/pull/10243)); thanks again for merging both. In #10243 I wrote that an adaptor for LaTeX buffers may follow later; this is it. The recipe is the same as those two, with `latex-to-svg-for-latex.el` in their place: same repository, [`alberti42/latex-to-svg`](https://github.com/alberti42/latex-to-svg), one file, and the core from [#10213](https://github.com/melpa/melpa/pull/10213) as its dependency.

### Brief summary of what the package does

As in the other two adaptors, the core is markup-agnostic, and the adaptor tells it which regions of the buffer to skip, then switches it on; it renders nothing itself (511 lines against 2469 in the core). It works in AUCTeX's `LaTeX-mode` and in the built-in `latex-mode`.

What it skips, so that math inside it is not previewed:

- **comments**, from an unescaped `%` to the end of the line, and `\begin{comment}` … `\end{comment}` and `\iffalse` … `\fi`.
- **verbatim environments and macros** — `verbatim`, `filecontents`, `\verb|…|` with any delimiter. With AUCTeX loaded, the lists come from AUCTeX's `LaTeX-verbatim-environments` and `LaTeX-verbatim-macros-with-delims`, so they include what its style files automatically add for the document's packages (e.g., the environment `lstlisting` when the document loads `listings` LaTeX package).
- **the preamble**, and what follows `\end{document}`, in a file that has `\begin{document}`. A file without `\begin{document}`, such as a chapter loaded with `\include` or `\input`, is all body.

Two things set it apart from the Org and Markdown adaptors:

- **References come from the document's `.aux` file.** `\ref` and `\eqref` show the **actual** number LaTeX printed in the PDF document, so references to sections, figures and labels in other `.tex` files (e.g., other chapters) resolve too, and a label the `.aux` file lacks shows `??`, as LaTeX does. The `.aux` file is found through a template the user sets, else through AUCTeX, which knows the document's main file and output directory, else next to the file. Clicking a reference jumps to its `\label`; for a label in another file it asks `xref`, so with eglot running texlab it opens the other file.
- **It keeps out of preview-latex's way.** While it is on, AUCTeX's preview-latex commands (`preview-at-point` and the others under `C-c C-p`) only say that they are off, since preview-latex would draw its own overlay images over the same source text.

Users enable it from the major mode's hook:

```elisp
(add-hook 'LaTeX-mode-hook #'latex-to-svg-for-latex-mode) ; AUCTeX
(add-hook 'latex-mode-hook #'latex-to-svg-for-latex-mode) ; built-in tex-mode.el
```

As in the other adaptors, the source stays in the buffer under the image, and a theme switch or a text zoom updates the previews from the backend's cache, with no LaTeX recompilation. A project's own macros are set per project, in `.dir-locals.el`.

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

It is one of three adaptors of the `latex-to-svg` stack, the rest of which you have already merged:

- [`latex-to-svg-backend`](https://melpa.org/#/latex-to-svg-backend) — the backend, which compiles LaTeX to SVG, [#10152](https://github.com/melpa/melpa/pull/10152).
- [`latex-to-svg-frontend`](https://melpa.org/#/latex-to-svg-frontend) — the markup-agnostic core, [#10213](https://github.com/melpa/melpa/pull/10213).
- [`latex-to-svg-for-org`](https://melpa.org/#/latex-to-svg-for-org) — the Org adaptor, [#10234](https://github.com/melpa/melpa/pull/10234).
- [`latex-to-svg-for-markdown`](https://melpa.org/#/latex-to-svg-for-markdown) — the Markdown adaptor, [#10243](https://github.com/melpa/melpa/pull/10243).
- **this package** — the LaTeX adaptor, its own recipe like the other two.

In LaTeX buffers, the package it compares with is AUCTeX's preview-latex, which also previews math in place, and since AUCTeX 14.1.1 (January 2026) can make SVG images too, through `dvisvgm`, as an option next to its default PNG. This package does not depend on AUCTeX: AUCTeX is optional, and its functions are called only when they are defined, as described above. What it offers in addition:

- **Previews are made and remade without a command.** preview-latex also shows an equation's source when the cursor enters its preview, but typesets only on command, and an edited equation keeps its old image or an icon until the next one. Here, the math renders when the buffer opens, and an edited equation renders again as the cursor leaves it.
- **`\ref` and `\eqref` show the numbers from the `.aux` file**, as text over the source, and a click jumps to the label, in another file through `xref`.
- **Padding, background and colour are display options**: changing them redraws the previews from the cache, with no LaTeX run, as a theme switch and a text zoom do.
- **The previews come from the backend's cache**, where each equation is named after its content: shared by all buffers and by `agent-shell-math-renderer`, kept across sessions, and cleaned of what has not been used for a while.
- **It is a thin layer**, 511 lines. For someone who already uses the Org or Markdown adaptor, it brings the same previews, cache and settings to LaTeX buffers, with nothing else to install.

What it lacks:

- **Equation numbers under `\numberwithin`.** preview-latex compiles the whole document, so its equation numbers follow `\numberwithin`, the LaTeX command that restarts the numbering in each chapter or section. By design, the package submitted in this PR typesets each equation on its own, as it is added or edited, without compiling the whole document, so its numbers run straight through, with no notion of which chapter or section they belong to: the fifth equation of chapter 3 shows (5) in a chapter file, instead of (3.5). References are right either way, since they come from the `.aux` file. Fixing the numbers inside the previews would mean tracking sections as well as equations, which would make the code much heavier for the few documents that use `\numberwithin`.

Both AUCTeX and this package speed up LaTeX with a format file (`.fmt`): the document's preamble is dumped once with TeX's `\dump`, and every later run loads it instead of reading the preamble again. I had long thought karthink and tecosaur brought this to Emacs, in their branch of Org that reworks its LaTeX preview, with SVG images that re-tint from the cache (Org has offered SVG through `dvisvgm` since its 9.0, AUCTeX since January 2026). Some code archaeology showed the format-file idea is much older: the technique is David Carlisle's `mylatex.ltx`, from 1994, when reading a long preamble took noticeable time on the computers of the day, and `preview-latex`, now part of AUCTeX, has used it since its release 0.7.4, on 2002-11-22. (side note: I started using Emacs in spring 2002, and missed this feature for all these years.)

[`agent-shell-math-renderer`](https://melpa.org/#/agent-shell-math-renderer), merged in [#10198](https://github.com/melpa/melpa/pull/10198), is the sibling front-end for [`agent-shell`](https://github.com/xenodium/agent-shell); it shares the backend and its on-disk cache with this package, not any code.

### 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 public Emacs API and, when AUCTeX is loaded, AUCTeX's documented functions (`TeX-master-output-file`, `LaTeX-verbatim-environments` and the like), each called only when it is defined.

### If you want to see it working

Both dependencies are in MELPA, so only this file has to come from the clone:

```elisp
;; latex and dvisvgm must be on exec-path
(package-install 'latex-to-svg-frontend) ; pulls latex-to-svg-backend
(add-to-list 'load-path "/path/to/clone/of/latex-to-svg")
(require 'latex-to-svg-for-latex)
(add-hook 'LaTeX-mode-hook #'latex-to-svg-for-latex-mode)
(add-hook 'latex-mode-hook #'latex-to-svg-for-latex-mode)
```

Then open `docs/example.tex` from the repository. Its references show `??` until the document is compiled; run `latex example.tex` twice, or `C-c C-c` in AUCTeX, and they show the numbers LaTeX printed.

### 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). The repository is; this adaptor is new: it was added on 2026-09-27 and first released in 0.18.0 the day after, together with the two core hooks it resolves references and jumps through. The rest of what it runs on, the core's detection, overlays, numbering and the backend's cache, is the code the Org and Markdown adaptors have used since August.
- [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)

Finally, I checked that `make recipes/latex-to-svg-for-latex` builds on both channels; `CHANNEL=stable` detects the current release, 0.18.1.

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

alberti42 — Mon, 28 Sep 2026 20:10:58 +0000

[pr-closed]: Add recipe for triode

kickingvegas — Sun, 04 Oct 2026 18:31:06 +0000

### Brief summary of what the package does

**triode.el** is a GNU Emacs remote control interface to the Triode app (), an internet radio station player for macOS.

### Direct link to the package repository

https://github.com/kickingvegas/triode

### Your association with the package

I am 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)
- [ ] 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] I understand the package must have 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 triode

kickingvegas — Mon, 28 Sep 2026 16:53:17 +0000

[pr-open]: Add recipe for fz-index

uppet — Mon, 28 Sep 2026 08:00:27 +0000

### Brief summary of what the package does

Sublime-style fuzzy file open (Goto Anything) backed by a native C dynamic module that holds the whole file index outside the Emacs Lisp heap. Stays responsive at Chromium scale (400k+ files: ~0.7 s cold index, 24–38 ms per keystroke), with Sublime-style scoring, background indexing, .gitignore support, preview and frecency.

The `:files` list includes the C source and Makefile because the package auto-installs its module on first use: a prebuilt binary (Linux/macOS/Windows, x86_64 + aarch64) is downloaded from GitHub Releases with SHA-256 verification, and the bundled source is compiled locally as fallback.

### Direct link to the package repository

https://github.com/uppet/fz-index

### 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) (GPL-3.0, LICENSE in the repo)
- [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) — `;; Assisted-by: Kimi Code CLI` under the Author line of fz-index.el; I reviewed every line before committing
- [x] The package has been maintained in a public repository for 1 month or more — the repository was created 2026-08-28 and has been public and maintained since (v0.3.1 → v0.3.2, with bug fixes reviewed and merged through CI). This is a resubmission of #10187, which was closed to wait out this requirement; per the reviewer's instruction I'm opening a new PR rather than asking for a reopen
- [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 (Emacs 28.2, 29.4, 30.2 in CI)
- [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) — `make recipes/fz-index` produced fz-index-20260924.814.tar with all intended files

[pr-closed]: Add recipe for md-preview

bvraghav — Sun, 27 Sep 2026 15:09:44 +0000

### Brief summary of what the package does

Live browser preview of Markdown (frontmatter, mermaid, KaTeX) for a buffer
(`md-preview-mode`) or a whole folder (`md-preview-folder`).

### Direct link to the package repository

https://github.com/bvraghav/md-preview

### 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] I understand the package must have 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)

The package runs the external `md-preview` command (pandoc + entr +
browser-sync), installed from source: https://bvraghav.github.io/md-preview/install.html
If the command is missing, the mode reports how to install it instead of failing.

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

bvraghav — Sun, 27 Sep 2026 13:43:41 +0000

[pr-open]: Add recipe for emjupy

mathren — Sun, 27 Sep 2026 04:41:38 +0000

### Brief summary of what the package does

`emjupy` is a package to run Jupyter notebooks in emacs aiming at retaining the native emacs editing experience and the convenience of notebooks for data exploration.

By design, it works with remote kernels using emacs built-ins (`eglot` and `tramp`, completion framework the way you like and configured, e.g., `vertico` + `corfu` + `orderless`+`xref`) while maintaining compatibility with standard `*.ipynb` for sharing with non-emacs users.

Inspired by the package `ein` but unlike it does not rely on polymode. Similar to `emacs-jupyter` and `ob-jupyter` in terms of interfacing emacs with jupyter, but different user case.

### Direct link to the package repository

https://github.com/mathren/emjupy

### Your association with the package

I'm the developer and maintainer

### Relevant communications with the upstream package maintainer

N/A

### 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] I understand the package must have 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-timegrid

Gleek — Sun, 27 Sep 2026 02:09:57 +0000

### Brief summary of what the package does

`org-timegrid` is a SVG week calendar for Org mode. It reads timed active
timestamps from your Org files and writes edits back to their source headings.

Create, move, resize, copy, rename, and remove calendar blocks with the mouse
or keyboard. The same renderer can add a compact, read-only day view to an
existing Org Agenda.

On Android, `org-timegrid` adds native touch scrolling and long-press editing

#### Similar packages:
- org-timeblock
- calfw + calfw-blocks
- org-timeline

### Direct link to the package repository

https://github.com/Gleek/org-timegrid

### 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] I understand the package must have 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-closed]: Add recipe for gptel-annotate

karthink — Sun, 04 Oct 2026 17:43:16 +0000

* recipes/gptel-annotate: Add recipe for gptel-annotate. gptel-annotate is a package for plumbing LLM responses (using gptel) as Flymake annotations.

### Brief summary of what the package does

> [!NOTE]
> Previously raised in #10167, re-raising here as it was closed because the package was too new.

gptel-annotate is an extension for [gptel](https://github.com/karthink/gptel) that allows you to use LLM responses to annotate buffers or files with suggestions, warnings or notes. It uses Emacs' built-in Flymake minor mode to display the LLM-generated diagnostics.

Reasoning: Sometimes the best view of an LLM's response is inline in buffer text, especially if its task directly relates to the buffer or file. (Fact checking, code explanations, writing critiques, etc.)

Alternatively, you can think of it as a bespoke Flymake backend that takes custom instructions.

### Direct link to the package repository

https://github.com/karthink/gptel-annotate

### 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 gptel-annotate

karthink — Fri, 25 Sep 2026 01:46:59 +0000

[pr-open]: Add recipe for tod

BuddhiLW — Thu, 24 Sep 2026 16:55:04 +0000

Depends on #10246 (Add recipe for clel): tod requires `clel`, the ClojureElisp
runtime. The repository became public on 2026-09-24, so this stays a draft
until clel is in MELPA and the month has passed (2026-10-24).

### Brief summary of what the package does

tod ("time of day") keeps the Emacs theme, and optionally the desktop
wallpaper, in step with the sun and the seasons at your location. It works
out the phase of the day (night, the three twilights, golden hour, day),
whether the sun is rising or setting, the astronomical season (flipped south
of the equator), the month and the calendar periods in effect, and ordered
rules in `tod-looks` turn that into a theme, a wallpaper, or a palette pywal
derives from the wallpaper, checked for WCAG contrast. `tod-mode` wakes at
every twilight boundary and at local midnight; `M-x tod-describe` shows the
sun, today's boundaries and the chosen look.

Similar packages: circadian.el and theme-changer switch between a day and a
night theme at sunrise and sunset; auto-dark follows the desktop's dark mode.
tod adds the twilight phases, seasons, months and holidays, wallpaper setters
for GNOME, KDE, Cinnamon, XFCE, sway, Hyprland and X11, and generated
contrast-checked palettes.

tod is written in ClojureElisp: every `tod*.el` is generated from
`src/**/*.cljel` in the same repository and committed.

### Direct link to the package repository

https://github.com/BuddhiLW/tod

### 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) (GPL-3.0-or-later)
- [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] I understand the package must have 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)

Local checks: CI runs byte-compile (warnings as errors), 62 ERT tests,
checkdoc and package-lint on Emacs 29.1, 30.1, 31.1 and snapshot; melpazoid
has no findings; `make recipes/clel recipes/tod` builds both from GitHub and
`package-install 'tod` into a fresh `package-user-dir` pulls in clel and
autoloads `tod-mode`.

[pr-closed]: Add recipe for clel

BuddhiLW — Sun, 04 Oct 2026 17:36:24 +0000

### Brief summary of what the package does

clel is the runtime library of [ClojureElisp](https://github.com/BuddhiLW/clojure-elisp),
a compiler from a Clojure dialect to Emacs Lisp. Code that ClojureElisp emits
calls clel for Clojure's data model and core library: maps kept as alists that
remember they are maps, sets, lazy sequences, `map`/`filter`/`reduce`/`partition`
and the rest of the sequence functions, `get-in`/`assoc-in`/`update-in`, atoms
and protocols.

clel.el is itself generated: ClojureElisp compiles it from
`resources/clojure-elisp/runtime.cljel`, and the generated file is committed.
The repository is the compiler (a Clojure project), so the recipe names the one
Emacs Lisp file with `:files`.

Similar packages: dash.el, seq.el and s.el cover parts of the same ground for
hand-written Emacs Lisp. clel follows Clojure's semantics (nil punning, lazy
sequences, keyword-keyed maps) because compiled code depends on them.

### Direct link to the package repository

https://github.com/BuddhiLW/clojure-elisp

### 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) (MIT)
- [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] I understand the package must have been maintained in a public repository for 1 month or more (public since 2026-01-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)

Local checks: melpazoid reports no byte-compile, checkdoc, package-lint or
load findings. Upstream CI byte-compiles clel.el with warnings as errors and
runs checkdoc and package-lint on Emacs 28.2, 29.1, 30.1 and 31.1 (`make
lint-elisp`; checkdoc before Emacs 31 checks more than melpazoid's Emacs, and
v0.8.1 fixed what it found). `make recipes/clel` builds from GitHub (v0.8.1,
54eb702) and `package-install` of the result into a fresh `package-user-dir`
works.

v0.8.2 (d4b00fd) adds the `Assisted-by:` lines under Author in clel.el; besides the version bump nothing else changes; upstream CI (byte-compile, checkdoc, package-lint on Emacs 28.2 to 31.1) passes on it.

[pr-open]: Add recipe for clel

BuddhiLW — Thu, 24 Sep 2026 16:39:13 +0000

[pr-closed]: Add recipe for dharmamitra

sebastian-nehrdich — Sun, 27 Sep 2026 16:21:00 +0000

### Brief summary of what the package does

`dharmamitra` provides grammar analysis and translation for Sanskrit, Pāli, Tibetan and Chinese texts from within Emacs, using the public API of https://dharmamitra.org (no API key required). For Sanskrit it shows segmentation, lemmatization, morphosyntactic tags and per-word dictionary glosses (DCS, Monier-Williams, Apte, Böhtlingk-Roth, Edgerton) in a dedicated `dharmamitra-text-mode` buffer; for all four languages it provides translations. Requests are asynchronous.

The related `dharmamitra-search` package (not on MELPA) covers semantic search over the same site; this package is complementary and does not overlap with existing MELPA packages.

### Direct link to the package repository

https://github.com/dharmamitra/dharmamitra-emacs

### Your association with the package

I am the author and maintainer of the package and of the Dharmamitra project.

### Relevant communications with the upstream package maintainer

**None needed** (I am the maintainer).

### 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] I understand the package must have been maintained in a public repository for 1 month or more (public since November 2024)
- [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) (`make recipes/dharmamitra` on both the unstable and stable channels; stable picks up tag `v0.2`)

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

[pr-open]: Add recipe for dharmamitra

sebastian-nehrdich — Thu, 24 Sep 2026 05:50:24 +0000

[pr-closed]: Add recipe for paren-solo

OverbearingPearl — Sun, 04 Oct 2026 17:29:23 +0000

### Brief summary of what the package does

Toggle Lisp code between compact (community standard) and dangling (each closing parenthesis on its own line) styles.

### Direct link to the package repository

https://github.com/OverbearingPearl/paren-solo

### 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] I understand the package must have 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 paren-solo

OverbearingPearl — Wed, 23 Sep 2026 15:25:31 +0000

[pr-closed]: Add recipe for latex-to-svg-for-markdown

alberti42 — Sun, 27 Sep 2026 16:01:33 +0000

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

This is the second of the two adaptors of the `latex-to-svg` front-end; the first, [`latex-to-svg-for-org`](https://melpa.org/#/latex-to-svg-for-org), you merged in [#10234](https://github.com/melpa/melpa/pull/10234); thanks again for reviewing and merging! This recipe is the same as that one, with `latex-to-svg-for-markdown.el` in place of `latex-to-svg-for-org.el`: same repository, [`alberti42/latex-to-svg`](https://github.com/alberti42/latex-to-svg), one file, and the core from [#10213](https://github.com/melpa/melpa/pull/10213) as its dependency. It packages the last file of that repository, so the `latex-to-svg-*` family is complete; an adaptor for LaTeX buffers may follow later.

### Brief summary of what the package does

As I wrote in #10234, the core is markup-agnostic: it never parses a specific markup itself, but asks the buffer's adaptor for the delimiters and the regions to skip. This adaptor is responsible for Markdown and switches the core on; it renders nothing itself (242 lines against 1815 in the core).

It tells the core which regions of a Markdown buffer are code, so that math inside them is not previewed. How it finds them depends on what the buffer's Emacs offers. With the `markdown` tree-sitter grammar installed — the normal setup for the modern `markdown-ts-mode`, which ships with Emacs 31.1 — it queries the parser for the code nodes. Without a grammar, as in the traditional `markdown-mode` and `gfm-mode`, equivalent regexps do the same work. Either way, what is excluded is:

- **fenced and indented code blocks** — both fence characters, a closing fence at least as long as the opening one, and 4-space / tab indented blocks, which have no delimiters at all;
- **inline code spans**, which are matched by regexp in both cases.

Users enable it from `markdown-ts-mode-hook`; `markdown-mode` and `gfm-mode` are supported too:

```elisp
(add-hook 'markdown-ts-mode-hook #'latex-to-svg-for-markdown-mode)
```

The source stays in the buffer under the image, so copy and save round-trip renderable LaTeX; a theme switch re-tints and a text zoom rescales the previews straight from the engine's cache, with no LaTeX recompilation.

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

It is the last layer of the `latex-to-svg` stack, the rest of which you have already merged:

- [`latex-to-svg-backend`](https://melpa.org/#/latex-to-svg-backend) — the rendering engine, [#10152](https://github.com/melpa/melpa/pull/10152).
- [`latex-to-svg-frontend`](https://melpa.org/#/latex-to-svg-frontend) — the markup-agnostic core, [#10213](https://github.com/melpa/melpa/pull/10213).
- [`latex-to-svg-for-org`](https://melpa.org/#/latex-to-svg-for-org) — the Org adaptor, [#10234](https://github.com/melpa/melpa/pull/10234).
- **this package** — the Markdown adaptor. Each adaptor is its own recipe so that a reader of one markup does not carry the other; the reasoning is in #10234.

[`agent-shell-math-renderer`](https://melpa.org/#/agent-shell-math-renderer), merged in [#10198](https://github.com/melpa/melpa/pull/10198), is the sibling front-end for [`agent-shell`](https://github.com/xenodium/agent-shell). It shares the engine and its on-disk cache with this package, not any code: an equation that appears both in your notes and in an agent's reply compiles only once.

### 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.

### If you want to see it working

Both dependencies are in MELPA, so only this file has to come from the clone:

```elisp
;; latex and dvisvgm must be on exec-path
(package-install 'latex-to-svg-frontend) ; pulls latex-to-svg-backend
(add-to-list 'load-path "/path/to/clone/of/latex-to-svg")
(require 'latex-to-svg-for-markdown)
(add-hook 'markdown-ts-mode-hook #'latex-to-svg-for-markdown-mode)
```

Then open `docs/example.md` from the repository, or any Markdown file with `$x^2$` or a `\begin{equation}` block. Switch your theme, or press `C-x C-+`, to see the previews follow without a recompile.

### 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)

`make recipes/latex-to-svg-for-markdown` builds on both channels; `CHANNEL=stable` detects the current release, 0.16.2.

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

alberti42 — Tue, 22 Sep 2026 11:21:09 +0000

[pr-closed]: Add recipe for consult-zoxide

agzam — Sun, 27 Sep 2026 15:59:56 +0000

### Brief summary of what the package does

Jump to a directory zoxide remembers, from a Consult prompt. Rows keep zoxide's ranking and show their score, and git checkouts also show the branch that's currently out. Narrowing keys pick out git roots, worktrees, or entries whose directory no longer exists - that last one so a database that's been filling up for a few years can actually be pruned.

Similar packages: [zoxide.el](https://git.sr.ht/~vonfry/zoxide.el) is already indexed here as `zoxide`, and it came first. It's the plain `completing-read` version with no dependencies, and it's the better pick for anyone not using Consult. Mine builds on Consult instead, for the annotations, narrowing and pruning; the README says so under "Prior art". [consult-dir](https://github.com/karthink/consult-dir) is adjacent rather than similar - there's an optional source that puts zoxide rows into its prompt.

### Direct link to the package repository

https://github.com/agzam/consult-zoxide.el

### 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] I understand the package must have 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 consult-zoxide

agzam — Mon, 21 Sep 2026 23:35:14 +0000

[pr-closed]: Update repository's default pull request template

riscy — Sun, 20 Sep 2026 21:59:54 +0000

Minor improvements to default pull request template -

- Use HTML comments so users don't (necessarily) have to delete guidelines
- Clarify "relevant communications" guideline, give a more common example
- Make unchecked boxes `[ ]` instead of `[]` so they render in as a box
- Add a link to the FAQ in the checklist guideline

Opening this as a PR to house any comments but I'll probably self-merge soon.

Edit:

- Also rephrased the 1-month checkbox for clarity (i.e. not optional)

[pr-open]: Update repository's default pull request template

riscy — Sun, 20 Sep 2026 20:56:21 +0000

[pr-closed]: Add recipe for flymake-biomejs

lina-bh — Sun, 20 Sep 2026 18:23:15 +0000

### Brief summary of what the package does

A Flymake backend for [Biome](https://biomejs.dev) using its JSON reporting mode.

### Direct link to the package repository

https://github.com/lina-bh/flymake-biomejs

### Your association with the package

Maintainer and sole contributor

### 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)
- [ ] 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 flymake-biomejs

lina-bh — Sun, 20 Sep 2026 14:39:26 +0000

[pr-closed]: Add recipe for nightpanel-theme

gregfelice — Sun, 20 Sep 2026 18:20:48 +0000

Third submission of the same one-line recipe, following #10137 and #10140. Both
were closed on the one-month rule. The repository has been public since
2026-08-01, so it is now seven weeks old.

> It's been a week now since the repo was created - please wait 3 more, and I
> promise I'll be prompt about getting to the review that week.
>
> — @riscy in #10140

@riscy asked for a fresh pull request when the time came, so here it is. The
recipe is unchanged.

### Brief summary of what the package does

`nightpanel-theme` is a dark theme modelled on a Saab instrument cluster seen at
night: a pure black canvas (`#0A0A0A`), instrument-scale green for body text,
and amber reserved for the things that would be a needle or a warning lamp on a
real dashboard — search matches, strings, constants, TODO keywords. Red appears
only for genuine errors. Comments and inactive chrome recede to a dim green so
the code itself is the brightest thing on screen.

Single file, no dependencies beyond Emacs 27.1. The floor comes from the
`tab-bar` and `tab-line` faces it styles.

### Direct link to the package repository

https://github.com/gregfelice/nightpanel-theme

### Your association with the package

Author and maintainer.

### Relevant communications with the upstream package maintainer

**None needed.** 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#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)

### Verification, re-run today against current `master`

| Check | Result |
| --- | --- |
| `package-lint` (latest from MELPA) | clean |
| `checkdoc` | clean |
| Byte-compile with `byte-compile-error-on-warn`, Emacs 30.1 | clean |

Both channels build from a clean checkout:

```
make recipes/nightpanel-theme -> nightpanel-theme-20260801.22.tar
make CHANNEL=stable recipes/nightpanel-theme -> nightpanel-theme-0.1.0.tar
```

`package-install-file` on the snapshot tar installs it, and `(load-theme
'nightpanel t)` then reports `custom-enabled-themes` as `(nightpanel)` with the
expected background.

### On AI assistance

The palette and the face definitions are mine. An AI assistant helped with the
packaging around them: header block, license boilerplate, autoload cookie,
commentary and README. I reviewed all of it. The
`Assisted-by: Claude:claude-opus-5` line sits under the Author line in the file,
per CONTRIBUTING.org.

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

[pr-open]: Add recipe for nightpanel-theme

gregfelice — Sun, 20 Sep 2026 05:13:19 +0000

[pr-closed]: Add recipe for magit-standup

raszi — Sun, 20 Sep 2026 18:19:16 +0000

### Brief summary of what the package does

`magit-standup` collects recent git commits from one or more repositories and
formats them as org-mode standup notes. It adds a transient menu that lets you
set the start date, the repositories, and the authors. On weekends and Mondays
it looks back to Friday. On other weekdays it looks back to the previous day.

### Direct link to the package repository

https://github.com/function-artisans/magit-standup

### 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)
- [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)

Closes function-artisans/magit-standup#3

[pr-open]: Add recipe for magit-standup

raszi — Sat, 19 Sep 2026 19:20:48 +0000

[issue-open]: RSS feed links always point to unstable melpa

Sat, 19 Sep 2026 18:03:41 +0000

# https://releases.melpa.org/updates.rss:

~~~ xml

xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
xmlns:atom="http://www.w3.org/2005/Atom">

MELPA package updates
https://melpa.org

en-us
40
News about package updates

hyperbole (9.1.0) --- GNU Hyperbole: The Everyday Hypertextual Information Manager
The hyperbole package has been updated to version 9.1.0.
Sat, 19 Sep 2026 18:03:41 +0000
https://melpa.org/packages/hyperbole-9.1.0.tar
https://melpa.org/#/hyperbole

~~~

All links should point to https://releases.melpa.org instead of https://melpa.org.

# https://snapshots.melpa.org/updates.rss:

~~~ xml

xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
xmlns:atom="http://www.w3.org/2005/Atom">

MELPA package updates
https://melpa.org

en-us
40
News about package updates

hyperbole (9.1.0.0.20260916.67) --- GNU Hyperbole: The Everyday Hypertextual Information Manager
The hyperbole package has been updated to version 9.1.0.0.20260916.67.
Sat, 19 Sep 2026 18:03:09 +0000
https://melpa.org/packages/hyperbole-9.1.0.0.20260916.67.tar
https://melpa.org/#/hyperbole

~~~

All links should point to https://snapshots.melpa.org instead of https://melpa.org.

cc @tarsius

hyperbole (9.1.0.0.20260916.67) --- GNU Hyperbole: The Everyday Hypertextual Information Manager

Sat, 19 Sep 2026 18:03:09 +0000

The hyperbole package has been updated to version 9.1.0.0.20260916.67.

[pr-open]: Add recipe for typst-overlay

hesampakdaman — Sat, 19 Sep 2026 12:31:49 +0000

### Brief summary of what the package does
Provides math overlays for Typst, similar to latex-preview.

### Direct link to the package repository

https://github.com/hesampakdaman/typst-overlay

### 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-closed]: Add recipe for adif

K6SM — Sun, 27 Sep 2026 15:57:38 +0000

### Brief summary of what the package does

A major mode for viewing and editing Amateur Data Interchange Format (ADIF) logs.

### Direct link to the package repository

https://github.com/K6SM/adif-mode

### Your association with the package

I'm the author/maintainer.

### Relevant communications with the upstream package maintainer

N/A

### 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 adif

K6SM — Fri, 18 Sep 2026 19:44:37 +0000