From: jamos@oboj.net
To: 9front@9front.org
Cc: knusbaum@sdf.org
Subject: No rendering of pages (Re: [9front] Netsurf 3.9 for Plan 9 (work in progress))
Date: Sat, 04 Jan 2020 15:41:42 +0200 [thread overview]
Message-ID: <3760784f04165b3e8f787dd2792e0dbb@oboj.net> (raw)
In-Reply-To: <A225D9EF-2ED3-4F07-AB8E-5DE93FC07D3D@sdf.org>
On 2020-01-03 05:12, Kyle Nusbaum wrote:
>
> I can't get the program to actually render anything,
> even file:/// resources, but I can see them getting fetched.
>
> I get CSSBase displayed at the bottom of the screen, seeming
> to correspond to the NSERROR_CSS_BASE error, but I can't figure
> out why that's happening. I'm guessing that's why nothing is
> rendered, but that may be a faulty assumption.
I moved to a completely different 9front installation, and found
out that I hardcode the path to the resources: NETSURF_FB_RESPATH
in the mkfile for the browser. If you have another installation
path than me (likely) you (right now) have to change that path to
correspond to where the 'res' directory is. At least things started
to render on my other installation when I changed this!
/Jonas
next prev parent reply other threads:[~2020-01-04 13:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 22:02 Netsurf 3.9 for Plan 9 (work in progress) jamos
2020-01-01 22:57 ` [9front] " ori
2020-01-02 0:59 ` jamos
2020-01-02 16:45 ` ori
2020-01-03 3:12 ` Kyle Nusbaum
2020-01-03 3:30 ` ori
2020-01-03 20:14 ` Kyle Nusbaum
2020-01-03 21:01 ` ori
2020-01-03 21:35 ` Kyle Nusbaum
2020-01-04 0:22 ` hiro
2020-01-04 10:21 ` Steve Simon
2020-01-04 13:41 ` jamos [this message]
2020-01-04 15:49 ` No rendering of pages (Re: [9front] Netsurf 3.9 for Plan 9 (work in progress)) ori
2020-01-04 12:08 ` [9front] Netsurf 3.9 for Plan 9 (work in progress) jamos
2020-01-04 17:14 ` ori
2020-01-04 21:33 ` jamos
2020-01-08 4:23 ` Kyle Nusbaum
2020-01-08 4:25 ` Kyle Nusbaum
2020-01-24 8:09 ` Eli Cohen
2020-01-24 10:09 ` hiro
2020-01-24 18:16 ` Kyle Nusbaum
2020-01-24 18:40 ` jamos
2020-01-25 15:11 ` Eli Cohen
2020-01-26 21:10 ` jamos
2020-01-29 20:42 ` Ori Bernstein
2020-02-03 16:00 ` ori
2020-02-04 20:19 ` Kyle Nusbaum
2020-02-04 20:11 ` ori
2020-02-04 20:29 ` Kyle Nusbaum
2020-01-03 10:39 ` telephil9
2020-01-03 10:44 ` telephil9
2020-01-03 15:07 ` ori
2020-01-03 15:14 ` telephil9
2020-01-03 11:55 ` Steve Simon
2020-01-03 15:08 ` telephil9
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=3760784f04165b3e8f787dd2792e0dbb@oboj.net \
--to=jamos@oboj.net \
--cc=9front@9front.org \
--cc=knusbaum@sdf.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).