unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Sébastien Lerique" <sl@eauchat.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Emacs on a reMarkable
Date: Thu, 07 Sep 2023 11:52:00 +0200	[thread overview]
Message-ID: <87lediwbm5.fsf@eauchat.org> (raw)
In-Reply-To: <86v8cou2jn.fsf@gmail.com>

Hi Simon!

Thank you for the answer!

On 05 Sep 2023 at 16:18, Simon Tournier <zimon.toutoune@gmail.com> wrote:

> Please consider I know nothing about reMarkable. :-)
>
>>   apt install guix
>>   guix pack -RR -S /emacsbin=bin emacs-no-x
>
> Here you are using emacs-no-x as it was with the release of Guix
> packaged by Debian.  Maybe you could run “guix pull” before running
> “guix pack”.
>

Aha, `guix pull` makes it work indeed! `emacs` or `emacs-no-x` made with
`-R` or `-RR` all work now.

> Just to be sure, could you share which revision (guix describe) of Guix
> you are using.  I mean, you are running emacs-no-x from which Guix
> revision?
>

After `guix pull` I'm at:

--8<---------------cut here---------------start------------->8---
root@arm-vm:~# guix describe
Generation 1	Sep 06 2023 17:05:27	(current)
  guix 65dcfb3
    repository URL: https://git.savannah.gnu.org/git/guix.git
    branch: master
    commit: 65dcfb3f3865d08467da747041263fd22460d393
--8<---------------cut here---------------end--------------->8---


In short, the setup now is:

1) Build and package Emacs in an ARM VM:

--8<---------------cut here---------------start------------->8---
root@arm-vm:~# apt install guix
root@arm-vm:~# guix pull
root@arm-vm:~# guix pack -R -S /emacsbin=bin emacs-no-x
--8<---------------cut here---------------end--------------->8---

2) Copy and un-tar it on the reMarkable, bind-mount /gnu, and run emacs either
through ssh or directly in Yaft:

--8<---------------cut here---------------start------------->8---
reMarkable: ~/ tar xf pszvzh7917kkf1cisxd46bx8vlac25zh-emacs-no-x-tarball-pack.tar.gz
reMarkable: ~/ mount -o bind /home/root/gnu /gnu
reMarkable: ~/ emacsbin/emacs
--8<---------------cut here---------------end--------------->8---


The challenge is that reMarkable doesn't provide a standard display, so
the terminal (Yaft) is still being developed (not by the company). Which
is why running some of the command lines can still be a challenge.

Let me know if anybody is interested in more details!


Now I have a final side question: after "guix pull" in the ARM VM, the
output of

  guix pack -RR -S /emacsbin=bin emacs-no-x

is still
"wpxqqdcslxxx9g9l9j847ifgh0xdlsfl-emacs-no-x-tarball-pack.tar.gz", i.e.
the same as before "guix pull". Is that normal?


Very best,
Sébastien


  reply	other threads:[~2023-09-07  9:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 13:26 Emacs on a reMarkable Sébastien Lerique
2023-09-05 14:18 ` Simon Tournier
2023-09-07  9:52   ` Sébastien Lerique [this message]
2023-09-11 16:26     ` Simon Tournier
2023-09-15 20:56       ` Sébastien Lerique
2023-09-18  8:50     ` Simon Tournier
2023-09-20 18:25       ` Sébastien Lerique
2023-09-21  7:14         ` Simon Tournier
2023-09-22  7:14           ` Sébastien Lerique

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lediwbm5.fsf@eauchat.org \
    --to=sl@eauchat.org \
    --cc=help-guix@gnu.org \
    --cc=zimon.toutoune@gmail.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).