From: David Masterson <dsmasterson@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Newest emacs version that can run on Ubuntu 18.04
Date: Sun, 19 Mar 2023 20:48:22 -0700 [thread overview]
Message-ID: <SJ0PR03MB5455338045F288900A147D2BA2809@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <87lejs15ky.fsf@yahoo.com> (Po Lu's message of "Mon, 20 Mar 2023 11:09:49 +0800")
Po Lu <luangruo@yahoo.com> writes:
> David Masterson <dsmasterson@gmail.com> writes:
>
>> Ack! This doesn't 'apt get' *all* the dependencies, correct? You've
>> already got a GTK and build environment installed, correct? Chromebook
>> Linux starts with a base environment that we have to install all the
>> dependencies by hand and use up limited space on the memory hard drive.
>> Suggestions on what to install w/o installing everything?
>
> People say it is easier to run feature/android on Chrome OS than to
> build Emacs for GNU/Linux.
>
> I don't use Chrome OS so I can't say as to how accurate that statement
> is.
Me either. I tried building Emacs v27 (I think) on Debian (Chromebook
Linux) and the dependencies for GTK were just too big and I wasn't sure
what I'd get without setting up GTK. So I wound up building Lucid Emacs
because the X-server was already there and the dependencies weren't too
big. I lost that build, though, when I power-washed the Chromebook, so
I've been using the pre-built 27.1 that you can get via 'apt install'.
Works, but I wish it supported speech-to-text (interestingly, running
'emacs -nw' on the console does support it).
I see an "Android Debug Bridge" in the Linux setup for the Chromebook,
but I don't know anything about Android.
--
David Masterson
next prev parent reply other threads:[~2023-03-20 3:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 20:46 Newest emacs version that can run on Ubuntu 18.04 Patrick Mahan
2023-03-16 21:26 ` Marcus Harnisch
2023-03-16 21:29 ` Óscar Fuentes
2023-03-16 21:49 ` Óscar Fuentes
2023-03-28 12:55 ` Byung-Hee HWANG
2023-03-16 21:58 ` christian de larrinaga via Users list for the GNU Emacs text editor
2023-03-16 22:30 ` Emanuel Berg
2023-03-20 1:38 ` David Masterson
2023-03-20 3:09 ` Po Lu
2023-03-20 3:48 ` David Masterson [this message]
2023-03-20 8:13 ` tomas
2023-03-17 1:57 ` Po Lu
2023-03-20 6:41 ` Michael Heerdegen
2023-03-23 0:38 ` David Masterson
2023-03-23 2:59 ` Michael Heerdegen
2023-03-28 13:26 ` Oleg Cherkasov
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=SJ0PR03MB5455338045F288900A147D2BA2809@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=luangruo@yahoo.com \
/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).