From: Alan Third <alan@idiocy.org>
To: Ahmed Khanzada <me@enzu.ru>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Fix misnamed variable breaking GNUstep Emacs.app build
Date: Sat, 18 Apr 2020 13:30:31 +0100 [thread overview]
Message-ID: <20200418123031.GA54322@breton.holly.idiocy.org> (raw)
In-Reply-To: <864kth1z8g.wl-me@enzu.ru>
On Fri, Apr 17, 2020 at 04:14:39PM -0700, Ahmed Khanzada wrote:
> After a recent refactor of ns_set_offset in nsterm.m, I noticed that the
> latest version of Emacs was not compiling under GNUstep.
>
> I believe that this patch should fix the problem, but it could use review
> from someone more familiar with the code. Emacs now compiles fine, and I
> am writing this very email in an Emacs compiled with this patch.
The fix looks good to me. If you want to create a proper patch (as
described in CONTRIBUTE) I’ll happily push it to the repository for
you.
> Additionally, if you need any help maintaining Emacs.app under GNUstep,
> please reach out to me. I am very interested, and I have already signed
> legal documents with the FSF to contribute to Emacs (and soon, GNUstep)
Any help with the NS port would be greatly appreciated. We do keep
compatibility with GNUstep, but most NS port development happens on
macOS, so silly mistakes in GNUstep code, like this one, tend to be
overlooked for a while.
Even raising bug reports for GNUstep would be a plus, since we seem to
have almost no users, and the only people who notice problems are
Emacs devs doing test builds.
--
Alan Third
next prev parent reply other threads:[~2020-04-18 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 23:14 [PATCH] Fix misnamed variable breaking GNUstep Emacs.app build Ahmed Khanzada
2020-04-18 12:30 ` Alan Third [this message]
2020-04-18 19:19 ` Ahmed Khanzada
2020-04-18 19:49 ` Alan Third
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=20200418123031.GA54322@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
--cc=me@enzu.ru \
/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.