unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Haiku port
Date: Thu, 26 Aug 2021 16:50:25 +0300	[thread overview]
Message-ID: <834kbctivy.fsf@gnu.org> (raw)
In-Reply-To: <87czq04a3v.fsf@yahoo.com> (message from Po Lu on Thu, 26 Aug 2021 21:19:16 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 26 Aug 2021 21:19:16 +0800
> 
> > Is haikufont so different from the other font infrastructures that you
> > couldn't do it?  Supporting HarfBuzz usually needs just a small number
> > of functions, as the basics are already in hbfont.c.
> >
> > Or maybe you have specific questions about this, in which case please
> > ask them.
> 
> BFont seems to be too basic.  Someone has given me details on using
> FreeType and HarfBuzz in Haiku applications and I plan to look at that.

Thanks.  Feel free to ask questions about that.

> > Hmm... maybe.  But then I guess I'm confused: what does the automatic
> > detection of Haiku do, if one needs --with-be-app to have the
> > windowing code?  IOW, why don't you assume --with-be-app if the
> > automatic detection of Haiku succeeds?
> 
> I think it owes to the fact that the Haiku windowing backend is not
> entirely complete.  Namely, the font driver needs work, and there are
> some things I haven't quite worked out, such as child frames.

So if one doesn't use --with-be-app, they get an Emacs that can only
support text-mode terminals, is that right?



  reply	other threads:[~2021-08-26 13:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87a6l47j32.fsf.ref@yahoo.com>
2021-08-26  7:37 ` Haiku port Po Lu via Emacs development discussions.
2021-08-26  7:51   ` Po Lu via Emacs development discussions.
2021-08-26  8:01     ` Po Lu via Emacs development discussions.
2021-08-26  9:13       ` Eli Zaretskii
2021-08-26  9:50         ` Po Lu via Emacs development discussions.
2021-08-26 11:26           ` Po Lu
2021-08-26 12:40           ` Eli Zaretskii
2021-08-26 13:19             ` Po Lu via Emacs development discussions.
2021-08-26 13:50               ` Eli Zaretskii [this message]
2021-08-27  0:14                 ` Po Lu
2021-08-27  6:36                   ` Eli Zaretskii
2021-08-28  6:19                     ` Po Lu via Emacs development discussions.
2021-08-26  8:39   ` Werner LEMBERG
2021-08-26  8:49     ` Po Lu

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=834kbctivy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).