From: fulton@fulton.software
To: 9front@9front.org
Subject: Re: [9front] Greetings! (and few questions)
Date: Thu, 10 Dec 2020 08:45:08 -0800 [thread overview]
Message-ID: <368DB9D4BB395B22F7A7A465EB711541@yourdomain.dom> (raw)
In-Reply-To: <CAL7Qv_NifU7Nzh9oOK=DtFr2nZm-tEUnnuE1xcvhf8bQjzRteg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
On your last question, any thing that file(1) returns as a `* plan 9 executable` should run as long as the arch is compatable with your kernel. Go (and plan9's linker) ouputs staticly linked executable's so it should be able to run on any plan9/9front machine.
- Fulton
[-- Attachment #2: Type: message/rfc822, Size: 3627 bytes --]
From: Bogunix M <bogunix@gmail.com>
To: 9front@9front.org
Subject: [9front] Greetings! (and few questions)
Date: Wed, 9 Dec 2020 22:43:34 -0800
Message-ID: <CAL7Qv_NifU7Nzh9oOK=DtFr2nZm-tEUnnuE1xcvhf8bQjzRteg@mail.gmail.com>
Good day!
I read the <9front dash1 manual> and fully understood the point <0.1.3
- Plan 9 is not for you>.
Still, I was wondering if you could help me with a little advice(s).
In particular, while playing with 9front I found myself looking for a
two-panel file manager and went on a quest to write one in Go.
Now, after having something breathing [1] and achieving
cross-compilation with Plan9, I discovered that this is not enough.
Current show-stopper is lack of Plan9 support by the underlying
library TCELL [2]. Issue is described in some details in [3] and [4]:
"...plan9 does not use escape sequences at all, nor does it use ttys.
It appears you need to interact directly with libdraw and with the
events subsystem..."
I am wondering if someone would be interested to contribute time to
explain the scope and potentially sketch the solution?
Another related question is whether Plan9, 64-bit binaries, compiled
by Go will work in 9front? The same question is currently unanswered
on Stackoverflow [5].
Sincerely,
Bogunix
[1] https://github.com/mushkevych/9ofm
[2] https://github.com/gdamore/tcell/
[3] https://github.com/gdamore/tcell/issues/402
[4] https://github.com/gdamore/tcell/issues/90
[5] https://stackoverflow.com/questions/65194285
next prev parent reply other threads:[~2020-12-10 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 6:43 Bogunix M
2020-12-10 7:19 ` Sean Hinchee
2020-12-10 7:33 ` Sean Hinchee
2020-12-10 11:05 ` Stuart Morrow
2020-12-10 14:18 ` telephil9
2020-12-10 15:00 ` Jacob Moody
2020-12-11 19:32 ` Daniel Moch
2020-12-13 7:09 ` Bogunix M
2020-12-13 7:36 ` Kurt H Maier
2020-12-10 16:45 ` fulton [this message]
2020-12-11 15:25 ` Kyle Nusbaum
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=368DB9D4BB395B22F7A7A465EB711541@yourdomain.dom \
--to=fulton@fulton.software \
--cc=9front@9front.org \
/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 NNTP newsgroup(s).