unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
Subject: Re: Carbon emacs - frame too big for minibuffer can't resize window
Date: Mon, 28 Feb 2005 01:59:38 +0100	[thread overview]
Message-ID: <x5ekf1ijnp.fsf@lola.goethe.zz> (raw)
In-Reply-To: mailman.1931.1109551850.32256.help-gnu-emacs@gnu.org

Peter Dyballa <Peter_Dyballa@Web.DE> writes:

> Am 28.02.2005 um 00:46 schrieb Stefan Monnier:
>
>> The Carbon Emacs code is in development, so you should try and help
>> fix the
>> bugs (and other misfeatures, mis-leading behaviors, ...), rather
>> than try
>> and work around them.  To fix the bugs, you should bring them to them
>> attention of developers.
>
> That's good news! I thought all Carbon development was 'migrated' to
> amateurs (those who do love), particularly in Japan, which produce a
> Carbon Emacs from CVS that Apple is advertising actively, and that
> this code won't migrate into the official code base.
>
> Carbon Emacs really needs a lot of development, particularly with
> fonts and fontsets. Latin and Unicode encodings are badly supported,
> only Mac-Roman and iso-2022-7bit (maybe 8bit too) work well -- at
> least with the fontsets I created from system fonts that are Unicode
> encoded. The HELLO file looks much to empty! But I have to admit
> that this fontsets things still have a lot of secrets for me ...

Are you sure we are talking about the same thing?  This sounds like
the old 20.7 Cocoa port.  The current developer version of Emacs
should compile on Carbon fine IIRC.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  parent reply	other threads:[~2005-02-28  0:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 17:25 Carbon emacs - frame too big for minibuffer can't resize window George Colpitts
2005-02-27 17:35 ` Peter Dyballa
     [not found] ` <mailman.1903.1109526710.32256.help-gnu-emacs@gnu.org>
2005-02-27 19:15   ` George Colpitts
2005-02-27 22:12 ` August
2005-02-27 22:38 ` Stefan Monnier
2005-02-27 23:25   ` Peter Dyballa
2005-02-27 23:46     ` Stefan Monnier
2005-02-28  0:17       ` Peter Dyballa
     [not found]       ` <mailman.1931.1109551850.32256.help-gnu-emacs@gnu.org>
2005-02-28  0:59         ` David Kastrup [this message]
2005-02-28  9:38           ` Peter Dyballa
2005-02-28 11:25           ` Piet van Oostrum
2005-02-28 11:47             ` David Kastrup
2005-02-28 12:56               ` Stefan Monnier
2005-02-28 12:54         ` Stefan Monnier
     [not found] ` <mailman.1926.1109544581.32256.help-gnu-emacs@gnu.org>
2005-02-28  0:46   ` George Colpitts
2005-02-28  1:49     ` Tim McNamara
2005-02-28 16:12     ` August
2005-02-28 16:40       ` Peter Dyballa
2005-02-28 17:50         ` August
2005-02-28 16:50     ` Drew Adams
     [not found]     ` <mailman.2013.1109608386.32256.help-gnu-emacs@gnu.org>
2005-03-02 13:02       ` Stefan Monnier
2005-03-02 15:22         ` August
     [not found]         ` <mailman.2325.1109778063.32256.help-gnu-emacs@gnu.org>
2005-03-04  0:29           ` Miles Bader

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=x5ekf1ijnp.fsf@lola.goethe.zz \
    --to=dak@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).