Re: Emacs Mac port

[YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>]

>>>>> On Sun, 03 Jan 2016 16:42:23 -0800, John Wiegley <jwiegley@gmail.com> said:

>> Do I need to elaborate this? When I receive a bug report, I try to
>> reproduce the bug on my side. If I have two variants of the Mac
>> port, restricted and fully-featured, then I have to try it for both
>> of the variants.

> You really only have to try it in your variant. Any of us on Mac
> will be trying to reproduce it in the restricted variant. If I
> believe it might be fixed in the fully-featured version, I'll try it
> there before notifying you about the bug.

> By moving your code into core, it should actually reduce your
> workload. There will be more eyes on your bugs, others verifying
> reproduction steps, more people to participate in the conversation,
> use of our bug tracker, etc.

> Come, Yamamoto-san, join us!!

I've been subscribing to the bug-gnu-emacs list, and occasionally try
to reproduce the reported NS port bugs on the Mac port, in case they
are common to OS X or Cocoa (e.g., bug#21573).  In a sense, I've
already been joining.

I really appreciate your encouragement, but I'm skeptical about
reduction of my workload by others' cooperation from my experience
with the Carbon port in Emacs 22 and the situation involving the NS
port especially with respect to GNUstep.

Also, frankly, I feel uncomfortable with aligning the current default
modifier key setting of the Mac port (Command -> Meta, Option ->
"compose") to that of the NS port (Command -> Super (emulating Mac
shortcut), Option -> Meta), which I don't think is a good default
especially for those who are using a keyboard that cannot enter all of
the ASCII characters without the option key.

I'd like to hear what others think.  Do you want to have a restricted
version of the Mac port in the mainline?  Will you use it in
preference to the full-feature version distributed separately (e.g.,
via another git repository)?

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp