unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Sébastien Kirche" <sebastien.kirche.no@spam.free.fr.invalid>
Subject: Re: emacs and osx
Date: Wed, 13 Apr 2005 16:53:06 +0200	[thread overview]
Message-ID: <m2k6n6u3sd.fsf@seki.fr> (raw)
In-Reply-To: _D97e.1227972$35.44954684@news4.tin.it

Le 13 Apr 2005, Bob Hunter a formulé :

> In principle, one  should be able to download the  latest from gnu and
> compile  autonomously  under  osx,   with  no  need  to  download  old
> out-of-sync binaries.

Practically, it is true.

You can checkout the cvs (i  dunno if there is some source snapshot from
cvs  at Gnu)  and  compile in  your own  system  and you  will obtain  a
functional Emacs in either X or Aqua flavors.

The  others ports  or projects  that you  mention  provide complementary
features  like  transparent  windows   or  better  support  for  eastern
languages like Japanese with correct display or input methods.

-- 
Sébastien Kirche

  parent reply	other threads:[~2005-04-13 14:53 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 14:02 emacs and osx Bob Hunter
2005-04-13 13:30 ` Gian Uberto Lauri
2005-04-13 14:56   ` Peter Dyballa
2005-04-13 14:53 ` Sébastien Kirche [this message]
2005-04-13 15:18 ` Jochem Huhmann
2005-04-13 15:44   ` Bob Hunter
2005-04-13 16:04   ` Bob Hunter
2005-04-13 16:27     ` David Kastrup
2005-04-13 16:38       ` Bob Hunter
2005-04-13 17:01         ` David Kastrup
2005-04-13 17:10           ` Lute Kamstra
2005-04-13 17:13             ` David Kastrup
2005-04-14  1:48           ` Miles Bader
2005-04-14  1:57           ` Miles Bader
2005-04-13 17:05         ` Lute Kamstra
2005-04-13 17:27       ` Peter Dyballa
2005-04-13 16:57     ` Lute Kamstra
2005-04-13 17:19       ` Bob Hunter
2005-04-13 17:52         ` David Kastrup
2005-04-13 18:08           ` Bob Hunter
2005-04-13 18:11             ` Bob Hunter
2005-04-13 18:21             ` David Kastrup
2005-04-13 18:34               ` Bob Hunter
2005-04-13 19:02                 ` Lute Kamstra
2005-04-13 21:01                   ` Ismael Valladolid Torres
     [not found]                   ` <mailman.1408.1113424532.2895.help-gnu-emacs@gnu.org>
2005-04-13 21:13                     ` David Kastrup
2005-04-13 22:51                       ` Joe Corneli
2005-04-13 19:19                 ` Thien-Thi Nguyen
2005-04-13 19:57                 ` David Kastrup
2005-04-13 23:46                   ` Bob Hunter
2005-04-13 17:19       ` Chris F.A. Johnson
2005-04-13 17:43         ` Eli Zaretskii
2005-04-13 18:44       ` Ismael Valladolid Torres
2005-04-13 19:21         ` emacs and osx, Tetris Peter Dyballa
     [not found]       ` <mailman.1392.1113416407.2895.help-gnu-emacs@gnu.org>
2005-04-13 19:07         ` emacs and osx Lute Kamstra
2005-04-13 20:04         ` David Kastrup
2005-04-22  7:48   ` Rogério Brito
2005-04-22 14:50     ` Chris Menzel
2005-04-25 21:08     ` Jochem Huhmann
2005-05-02  0:29       ` Stefan Monnier

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=m2k6n6u3sd.fsf@seki.fr \
    --to=sebastien.kirche.no@spam.free.fr.invalid \
    --cc=sebastien.kirche@free.fr \
    /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).