all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Charles Choi <kickingvegas@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Willing to Contribute to Emacs NS-Port Development
Date: Tue, 6 Aug 2024 13:28:29 -0700	[thread overview]
Message-ID: <1EA54CAB-DC46-498B-962E-CDBC57D3F2D5@gmail.com> (raw)
In-Reply-To: <m2a5hp94u5.fsf@pro2.fritz.box>

While I do find it somewhat distressing that there are no maintainers for the Cocoa port (is that really true?), I wonder if there are any metrics to support the assertion that the current Cocoa port is unstable. While I don't regularly use the macOS build distributed by GNU, I do use daily the Mitsuharu fork of Emacs on macOS without surprise and have done so for years. Even that though is anecdotal. Are there tickets to back up the story of unstable macOS behavior?

- Charles

—
Charles Y. Choi, Ph.D.
kickingvegas@gmail.com



> On Aug 6, 2024, at 6:08 AM, Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
> 
> I'm not an Emacs maintainer. I'm a macOS user, exclusively, and
> sometimes I'm contributing this or that.
> 
> From my POV, what is missing are Cocoa (macOS GUI) developers. The Cocoa
> port is unmaintained and has serious stability problems, i.e. it freezes
> and crashes much too frequently on macOS.
> 
> Without someone familiar with Cocoa who can fix things, testing won't
> help much.
> 
> My 2 cents only, of course.





  reply	other threads:[~2024-08-06 20:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 10:38 Willing to Contribute to Emacs NS-Port Development Vardhamann B E
2024-08-06 13:08 ` Gerd Möllmann
2024-08-06 20:28   ` Charles Choi [this message]
2024-08-07  0:55     ` Po Lu
2024-08-07  2:53       ` Charles Choi
2024-08-22 20:19         ` chad
2024-08-06 22:00 ` Andrea Corallo
2024-08-17  9:20 ` Eli Zaretskii

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=1EA54CAB-DC46-498B-962E-CDBC57D3F2D5@gmail.com \
    --to=kickingvegas@gmail.com \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.