CVE and update status of the FreeBSD ports tree3,864 unaddressed CVEs in 671 portsAll times are CET
Port details

misc/emacs-libvterm g20251119_2

Emacs libvterm integration

Port info

Maintainer
tslight@pm.me
Packages
latest: g20251119_2
Upstream
up to date
Last update
to g20251119_2 · e561a50b04
Quarterly
2026Q4: g20251119_2
WWW
https://github.com/akermu/emacs-libvterm/
Links
cgit · VuXML

Install

Package
# pkg install emacs-libvterm
installs g20251119_2 from latest; from quarterly (2026Q4) g20251119_2
Port
# cd /usr/ports/misc/emacs-libvterm && make install clean
Size
44 KiB download · 146 KiB installed
Depends on
devel/libvterm 0.3.3
License
GPLv3+
pkg-message
Shown after installing
Final emacs-libvterm setup instructions:

Add (require 'vterm) to your Emacs configuration.

M-x 'vterm' to open a new terminal.
Shown after upgrading
The emacs-libvterm shell-integration scripts have moved:

old:  /usr/local/share/emacs/site-lisp/etc/
new:  /usr/local/share/emacs/site-lisp/vterm/etc/

If you source emacs-vterm-bash.sh, emacs-vterm-zsh.sh, or
emacs-vterm.fish from your shell startup file (e.g. .bashrc, .zshrc, or
config.fish), update the path accordingly.

Packages by version and architecture

latest

FreeBSD versionamd64aarch64i386
FreeBSD 16g20251119_2g20251119_2–
FreeBSD 15g20251119_2g20251119_2–
FreeBSD 14g20251119_2g20251119_2g20251119_2

quarterly (2026Q4)

FreeBSD versionamd64aarch64i386
FreeBSD 15g20251119_2g20251119_2–
FreeBSD 14g20251119_2g20251119_2g20251119_2

version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.

Unaddressed and VuXML only (0)

No unaddressed CVE and nothing reported by pkg audit for the packaged version g20251119_2.

Fixed (0)

No VuXML entries for this package.

Problem reports (0) · open in Bugzilla, most recently changed first

None.

Commits (3)

Joseph Mingrone (jrm) · g20251119_2
misc/emacs-libvterm: Install etc/ under the vterm/

Previously, the shell-integration scripts (emacs-vterm-bash.sh,
emacs-vterm-zsh.sh, emacs-vterm.fish) were installed under
${EMACS_SITE_LISPDIR}/etc/, i.e. share/emacs/site-lisp/etc/.  That is a
shared, generically-named directory, and creating it cause problems for
at least one other package [0].

Install everything under ${EMACS_SITE_LISPDIR}/vterm/ instead.  This
keeps the port self-contained, no longer pollutes a directory other
ports probe, and matches ELPA package's layout.

[0]
math/ess auto-detects ess-etc-directory by probing paths relative to its
own lisp directory, one of which is ../etc.  With site-lisp/etc present,
ESS selected it instead of the correct share/emacs/etc/ess, so M-x R
failed to load ESSR with "cannot open the connection".

Approved by:	maintainer timeout
Sponsored by:	The FreeBSD Foundation
Pull Request:	https://github.com/freebsd/freebsd-ports/pull/568
e561a50b04
Joseph Mingrone (jrm) · g20251119_1
Emacs Lisp ports framework: Overhaul

This overhaul introduces four key changes to the elisp ports framework:

1. Remove support for packaged byte-compiled elisp.

   The primary motivation is to remove a large number of flavor-specific
   packages and to simplify the ports tree.  As an example, supporting
   byte-compiled elisp for devel/tablist required six packages, one for
   each flavor of editors/emacs and editors/emacs-devel.  With over 100
   elisp ports and requests for new Emacs flavors, this was
   unmanageable.

2. Install configuration to integrate with Emacs's native compilation
   machinery, allowing elisp from ports to be compiled into the standard
   cache under the user's home directory.

   This matches the behavior of GNU ELPA packages and generally results
   in a faster experience.  Speedups vary depending on the
   characteristics of the elisp code, but are often reported to be 2.5
   to 5 times faster than byte-compiled code.

3. Perform byte compilation on the target host, but only when native
   compilation is unavailable.  Compilation is initiated when Emacs
   starts, and the resulting .elc files are cached under the user's
   home directory.

4. Load all autoload files installed by FreeBSD elisp ports.  This
   mirrors what package.el does for ELPA packages, ensuring that
   autoloaded functions are available without requiring users to
   explicitly load each package.

Users with elisp packages (*-emacs_*) installed should consult the
2026-04-11 UPDATING entry for instructions on handling the transition.

Reviewed by:	ashish, Benjamin Jacobs <freebsd@dev.thsi.be>, dinoex,
		mandree, mce, nobutaka, Pat Maddox <pat@patmaddox.com>,
		rhurlin
Sponsored by:	The FreeBSD Foundation
Differential Revision:	https://reviews.freebsd.org/D56001
bc45b7ec88
Joseph Mingrone (jrm) · g20251119
misc/emacs-libvterm: New port for Emacs libvterm integration

Emacs-libvterm (vterm) is fully-fledged terminal emulator inside GNU
Emacs based on libvterm, a C library. As a result of using compiled
code (instead of elisp), emacs-libvterm is fully capable, fast, and it
can seamlessly handle large outputs.

Reviewed by:	jrm
Pull Request:	https://github.com/freebsd/freebsd-ports/pull/480
f13b9e1698