From: Bozhidar Batsov <bozhidar@batsov.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Jan Djärv" <jan.h.d@swipnet.se>,
"João Távora" <joaotavora@gmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Visual bell patch for emacs on OSX
Date: Wed, 18 Dec 2013 16:52:24 +0200 [thread overview]
Message-ID: <D86E198B84A0487490CF0CA77CEF7A15@gmail.com> (raw)
In-Reply-To: <jwv8uvikzyq.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
On Wednesday, December 18, 2013 at 4:21 PM, Stefan Monnier wrote:
> > Seems to me that GNUStep is killing the user experience of the people that
> > are actually using the NS port.
> >
>
>
> WTF? How do you get to this conclusion? The OP has already been told
> that it's perfectly OK to just ifdef out the NS-only code.
>
>
I guess I misinterpreted the last few mails in the discussion. I was left under the impression that only
code compatible with GNUStep is eligible for inclusion in Emacs.
>
> > Maybe this is a policy worth revisiting for the sake of the people
> > that use the NS port?
> >
>
>
> People who use the NS port and aren't satisfied with it should start
> contributing code, because we really don't have nearly
> enough contributors. As Jan pointed out, a non-negligible fraction of
> bugs fixed in the NS code are due to Jan who could only do that thanks
> to the GNUstep support, so claiming that the GNUstep support is killing
> the NS port is ridiculous.
>
>
Fair points - I wasn’t aware of the lack of NS contributions. Admittedly I’m not overly familiar with the NS port, having used Emacs mostly on GNU/Linux.
I know, however, there is some enhanced NS port of Emacs (https://github.com/railwaycat/emacs-mac-port) and I wonder
why aren’t the (some) patches from it applied upstream.
Anyways, I’m dabbling into Objective-C and Cocoa right now. If I manage to grok them I might try to contribute to the NS port.
Please, accept my apologies, if I offended someone. I meant no disrespect.
>
>
> Stefan
[-- Attachment #2: Type: text/html, Size: 2999 bytes --]
next prev parent reply other threads:[~2013-12-18 14:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 22:45 Visual bell patch for emacs on OSX João Távora
2013-12-16 23:05 ` Glenn Morris
2013-12-16 23:46 ` Glenn Morris
2013-12-16 23:49 ` João Távora
2013-12-17 0:14 ` Glenn Morris
2013-12-17 2:11 ` Stefan Monnier
2013-12-17 16:59 ` Jan Djärv
2013-12-18 12:52 ` Bozhidar Batsov
2013-12-18 14:21 ` Stefan Monnier
2013-12-18 14:52 ` Bozhidar Batsov [this message]
2013-12-18 15:16 ` Jan Djärv
2013-12-21 0:11 ` João Távora
2013-12-21 8:19 ` Jan Djärv
2013-12-23 12:09 ` Jan Djärv
2013-12-24 9:56 ` João Távora
2013-12-25 16:30 ` Jan Djärv
2013-12-21 8:56 ` martin rudalics
-- strict thread matches above, loose matches on Subject: below --
2013-12-17 8:35 François-Xavier Bois
2013-12-17 15:11 ` Jan Djärv
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=D86E198B84A0487490CF0CA77CEF7A15@gmail.com \
--to=bozhidar@batsov.com \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.