From: 岡本健二 <keoknj55@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
Date: Tue, 7 May 2019 12:48:48 +0900 [thread overview]
Message-ID: <CA+_tt6JoV4-3=TM3j_3VYF0r5F0R-3HfbZoBiWxn4nY8cgTzUg@mail.gmail.com> (raw)
In-Reply-To: <CAJSxfmLOpzbLin7k8WRAK-UdyQwEUreJ5MGnANpMVe43oCo7SA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
I made wio on ubuntu 18.04, and confirmed wio can run nested.
It looks like Plan 9's rio!
To compile wio, especially wiroots on 18.04, we have to make meson wlroots
cage alacritty wayland-protocols for more recent versions.
Kenji
2019年5月3日(金) 9:49 Skip Tavakkolian <skip.tavakkolian@gmail.com>:
> One person's epiphany is another's afterthought.
>
> (I've been conditioned by Twitter to not read anything longer than 240
> chars. Ditto for responses. I can't speak to points you made later)
>
> On Thu, May 2, 2019, 1:21 PM hiro <23hiro@gmail.com> wrote:
>
>> > Broadly speaking, that's [rio running inside rio] the essence of Rio.
>>
>> they makes no sense to me, that rio nesting feature seems like an
>> afterthought and involves a lot of back and forth which isn't just
>> inefficient, but extremely inflexible!
>>
>>
[-- Attachment #2: Type: text/html, Size: 1569 bytes --]
next prev parent reply other threads:[~2019-05-07 3:48 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 4:12 Ryan Gonzalez
2019-05-02 4:17 ` Rodrigo G. López
2019-05-02 4:36 ` Skip Tavakkolian
2019-05-02 4:56 ` David Arnold
2019-05-02 7:13 ` Fazlul Shahriar
2019-05-02 11:15 ` hiro
2019-05-02 11:10 ` hiro
2019-05-02 14:07 ` hiro
2019-05-03 0:47 ` Skip Tavakkolian
2019-05-03 1:27 ` Dan Cross
2019-05-03 7:59 ` hiro
2019-05-03 8:20 ` hiro
2019-05-03 11:52 ` Lucio De Re
2019-05-03 12:32 ` hiro
2019-05-03 12:35 ` hiro
2019-05-03 17:01 ` Lucio De Re
2019-05-04 20:53 ` hiro
2019-05-05 3:19 ` Lucio De Re
2019-05-05 7:51 ` hiro
2019-05-05 8:34 ` Lucio De Re
2019-05-03 23:08 ` Ethan Gardener
2019-05-04 5:55 ` Jens Staal
2019-05-04 7:04 ` hiro
2019-05-07 3:48 ` 岡本健二 [this message]
2019-05-03 2:06 ` Bakul Shah
2019-05-04 22:47 umbraticus
2019-05-05 7:53 ` hiro
2019-05-05 9:33 ` Lucio De Re
2019-05-05 10:01 ` hiro
2019-05-05 10:15 ` Lucio De Re
2019-05-05 11:09 ` hiro
2019-05-04 22:53 umbraticus
2019-05-05 12:32 cinap_lenrek
2019-05-05 13:50 ` Jens Staal
2019-05-05 17:16 ` hiro
2019-05-05 13:53 ` Lucio De Re
2019-05-05 15:14 ` Lucio De Re
2019-05-07 4:15 ` Lucio De Re
2019-05-08 12:32 ` Ethan Gardener
2019-05-09 7:39 ` Lucio De Re
2019-05-09 9:37 ` hiro
2019-05-05 14:14 cinap_lenrek
2019-05-05 15:59 ` Jens Staal
2019-05-05 15:11 cinap_lenrek
2019-05-05 15:22 cinap_lenrek
2019-05-05 15:32 ` Lucio De Re
2019-05-07 5:40 cinap_lenrek
2019-05-07 14:15 ` Lucio De Re
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='CA+_tt6JoV4-3=TM3j_3VYF0r5F0R-3HfbZoBiWxn4nY8cgTzUg@mail.gmail.com' \
--to=keoknj55@gmail.com \
--cc=9fans@9fans.net \
/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).