<a target="_blank" href="https://duckduckgo.com/?q=emacs-vterm&amp;t=osx">VTerm</a> won't work OOTB on my emacs 28 with byte compilation, presumably because the compilation of the <code>emacs-vterm</code> module is hacked around in the doom VTerm module.
Emacs complains that It can't find the VTerm module.
So we need to build that module manually:
<pre><code class="lang-bash">$ brew install libvterm
$ cd develop/emacs
$ git clone https://github.com/akermu/emacs-libvterm.git
$ cd emacs-libvterm
$ mkdir -p build
$ cd build
$ cmake ..
$ make
</code></pre>
Now we need to tell emacs how to find the VTerm module. I added this on the top of my <code>~/.doom.d/config.el</code>:
<pre><code class="lang-plaintext">(add-to-list 'load-path "~/develop/emacs/emacs-libvterm")
</code></pre>
After this, <code>VTerm</code> works. Toggling the terminal is <code>SPC o t</code>.

[VTerm](https://duckduckgo.com/?q=emacs-vterm&t=osx) won't work OOTB on my emacs 28 with byte compilation, presumably because the compilation of the `emacs-vterm` module is hacked around in the doom VTerm module.

Emacs complains that It can't find the VTerm module.

So we need to build that module manually:

```bash
$ brew install libvterm
$ cd develop/emacs
$ git clone https://github.com/akermu/emacs-libvterm.git
$ cd emacs-libvterm
$ mkdir -p build
$ cd build
$ cmake ..
$ make
```

Now we need to tell emacs how to find the VTerm module. I added this on the top of my `~/.doom.d/config.el`:

```plaintext
(add-to-list 'load-path "~/develop/emacs/emacs-libvterm")
```

After this, `VTerm` works. Toggling the terminal is `SPC o t`.

VTerm in DOOM Emacs