From: "Philip Silva via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] amd64 bootstrap file fo go1.16.3
Date: Sun, 18 Apr 2021 08:36:09 +0000 [thread overview]
Message-ID: <bnD-P3DDSzw2AXe_OMS1pf9I5ARahubF4NWurYbJjRiH31R1Z_NSgVrJ9c8-6AFnABXRamhXLLxuwF3_6TwSTvaDcDdsqwtwTHlCS84ZMY4=@protonmail.com> (raw)
In-Reply-To: <931579D0DE2DAE4589C803B8B49D8994@hera.eonet.ne.jp>
About Go 1.16.3, I had initially another problem when compiling. While running the compiler expected the bootstrapping files to be in a certain path. I think something like /tmp/glenda/.../..., so I renamed the path and it worked. I didn't check further though, but I'll check again later. Otherwise it worked, although I only did make.rc without the tests.
True, I noticed for instance light grey tones might show up as white. That's on a external Dell screen which is not the newest. On the fancy Macbook Air screen it's the grey. (E.g. on google.com, which is supposed to have a white background anyway ;)) The conversion from hex to draw.Color is really crude right now, so maybe it only works when the screen has a lot of gamut. Apart from that both vesa modes 1280x800x32 and 1920x1080x32 work for me, but only tested so far with VMWare and drawterm. Hm, does it not render at all then at 1920x1080x32?
> JS support of opossum becomes much better...
Awesome! Yeah quite some changes have happened on the JS side, really experimental AJAX support is also there. (On golang.org e.g. it's possible to run the example) Although right now I'm thinking to put the JS side into a separate process or even fs. That would reduce command line flags and all the messiness of js (support) itself. Apart from that a lot of issues about flickering (scrolling, loading text) and font sizing had been improved.
Greetings, Philip
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Am Sonntag, 18 April 2021 06:05 schrieb <kokamoto@hera.eonet.ne.jp>:
> I forgot to write that opossum-master runs successfull partially.
> 'Partially' means the color is a little bit wrong, and I cannot use vesa mode
> on 1920x1080x32, can do just under 1280x1024, and now using it
> as 1024x768x32(sigh).
>
> JS support of opossum becomes much better...
>
> Kenji
>
>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/T75ee4ccd407669dd-M065cb7408d643eb1ec0c5aea
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T75ee4ccd407669dd-Mc5a0258f7a1ab7d69f7c0597
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-04-18 8:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 0:28 kokamoto
2021-04-18 4:05 ` kokamoto
2021-04-18 8:36 ` Philip Silva via 9fans [this message]
2021-04-18 22:36 ` kokamoto
2021-04-19 23:02 ` kokamoto
2021-04-20 7:24 ` David du Colombier
2021-04-20 23:03 ` kokamoto
2021-04-27 6:00 ` kokamoto
2021-04-27 7:01 ` David du Colombier
2021-04-21 9:39 ` Richard Miller
2021-04-21 14:27 ` Bakul Shah
2021-04-21 15:04 ` Richard Miller
2021-04-20 23:05 ` kokamoto
2021-04-21 5:23 ` kokamoto
2021-04-21 6:56 ` David du Colombier
2021-04-21 9:20 ` kokamoto
2021-04-21 9:29 ` Richard Miller
2021-04-21 11:04 ` kokamoto
2021-04-18 9:08 ` David du Colombier
2021-04-18 10:19 ` kokamoto
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='bnD-P3DDSzw2AXe_OMS1pf9I5ARahubF4NWurYbJjRiH31R1Z_NSgVrJ9c8-6AFnABXRamhXLLxuwF3_6TwSTvaDcDdsqwtwTHlCS84ZMY4=@protonmail.com' \
--to=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).