9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Eli Cohen <echoline@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] netsurf native frontend
Date: Fri, 22 May 2020 23:13:45 -0700	[thread overview]
Message-ID: <CAHwi9bwLxFm76MdTLUe2bPuQ=QH8sV9FLPfjmAbUh9Xer0DVNw@mail.gmail.com> (raw)
In-Reply-To: <B3F7C3D5177DD59B998EE4CD8699D9F4@hera.eonet.ne.jp>

I'm having trouble getting this working. it gets stuck when I first
open it, at the bottom it says "loading" and never loads. I had this
problem with nsfb before I ran mk 9res, but I can't figure out what
I'm doing wrong here.

On Fri, May 22, 2020 at 9:08 PM <kokamoto@hera.eonet.ne.jp> wrote:
>
> > would like to have some feedback on this.
>
> I don't know why you implemented this, what was your
> dislike point of the framebuffer netsurf?
>
> By the way, I can input 日本語(Japanese) into the google
> search window of the opening panel, without to compile
> for freetype Japanese fonts.
>
> Kenji
>


-- 
http://echoline.org


  reply	other threads:[~2020-05-23  6:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 15:54 telephil9
2020-05-21 16:06 ` [9front] " hiro
2020-05-21 17:59 ` Romano
2020-07-28  7:11   ` [9front] netsurf native frontend (text_insert: illegal combination FCVTZSDW FCON NONE REG) Romano
2020-07-29  6:08     ` arm64 fails to link when float converted to int (Was Re: [9front] netsurf native frontend (text_insert: illegal combination FCVTZSDW FCON NONE REG)) Romano
2020-08-01 11:43       ` cinap_lenrek
2020-08-01 12:23         ` Anthony Martin
2020-05-21 21:16 ` [9front] netsurf native frontend Dave MacFarlane
2020-05-23 11:03   ` telephil9
2020-05-23 15:42     ` Stanley Lieber
2020-05-23 16:13     ` Stanley Lieber
2020-05-23  4:08 ` kokamoto
2020-05-23  6:13   ` Eli Cohen [this message]
2020-05-23  6:18     ` telephil9
2020-05-23  6:37       ` Eli Cohen
2020-05-23 20:10   ` jamos
2020-05-24  0:02     ` kokamoto
2020-05-25  3:51       ` kokamoto
2020-05-24  2:13 ` sl

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='CAHwi9bwLxFm76MdTLUe2bPuQ=QH8sV9FLPfjmAbUh9Xer0DVNw@mail.gmail.com' \
    --to=echoline@gmail.com \
    --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).