From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: vterm-module compile error
Date: Fri, 30 Oct 2020 03:52:19 +0100 [thread overview]
Message-ID: <878sbos9wc.fsf@zoho.eu> (raw)
In-Reply-To: 87mu08o6it.fsf@zoho.eu
>> I am using it from git sources and it works without problems that
>> way. It does not work when installed as package.
>
> Thanks, I'll check it out, Gw! :)
It seems this is what God wanted to happen...
Here is what the developers say:
Some distributions (e.g. Ubuntu < 20.04, Debian Stable) have
versions of libvterm that are too old. If you find compilation
errors related to VTERM_COLOR, you should not use your system
libvterm. See FAQ for more details. [1]
I didn't find the FAQ ("no such anchor"), but the developers also say:
If not available, libvterm will be downloaded during the
compilation process. [1]
So what I did, I simply removed the repos' libvterm
$ sudo apt-get remove libvterm0 libvterm-bin libvterm-dev
Then I deleted vterm from the Emacs package manager, and installed
it again. Now it gets an up-to-date libvterm from git, and all you
have to do is M-x vterm RET to start it. Wonderful!
Now everyone is thinking ... if it can do all that, why can't it
examine the installed libvterm, first thing? I don't know, but cool
that it works anyway.
Yes, at a glance vterm seems much faster and more robust than the
built-in alternatives.
[1] https://github.com/akermu/emacs-libvterm
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
next prev parent reply other threads:[~2020-10-30 2:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 0:26 vterm-module compile error Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-24 12:23 ` Jean Louis
2020-10-24 12:34 ` Tassilo Horn
2020-10-24 13:11 ` Jean Louis
2020-10-27 0:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-30 2:52 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2020-10-30 5:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-30 6:11 ` Jean Louis
2020-10-30 6:30 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-30 9:04 ` Jean Louis
2020-11-01 0:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 0:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 6:21 ` Jean Louis
2020-11-01 11:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 12:43 ` Jean Louis
2020-11-01 13:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 13:17 ` Jean Louis
2020-11-01 13:30 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 15:38 ` Jean Louis
2020-11-01 16:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 16:24 ` Jean Louis
2020-11-01 18:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 21:45 ` Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878sbos9wc.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).