all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ben McGinnes <ben@adversary.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs 26 MacOS bugs
Date: Wed, 7 Feb 2018 13:13:01 +1100	[thread overview]
Message-ID: <20180207021301.zpvpexdkewztqxo4@adversary.org> (raw)
In-Reply-To: <CAM-tV--R5kModXYszZCqr1ND21X+oSBqUFDcswnrjQzuD5RrJw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2034 bytes --]

On Tue, Feb 06, 2018 at 08:33:31PM -0500, Noam Postavsky wrote:
> On Tue, Feb 6, 2018 at 7:43 PM, Ben McGinnes <ben@adversary.org> wrote:
> 
> > Sure, how many current OS X bugs have already been reported and which
> > ones are they?
> 
> Approximately these ones:
> https://debbugs.gnu.org/cgi/pkgreport.cgi?include=subject%3Amacos;include=subject%3Aosx;package=emacs

Cheers.

>>  I also want to be sure I'm not simply duplicating existing
>> reported bugs.
> 
> Too late! You already reported it by sending it here. ;)

Heh.  Of course ...

>>  Nor do I know how pressing the release date for version 26 is, if
>> it's even locked in at all.
> 
> AFAIK, there's no firm date, but emacs-26 is in feature freeze and
> only taking very safe/urgent bug fixes. So it's possible these bugs
> won't be fixed until after 26.1

I think I could make a very convincing argument regarding the modifier
keys here being urgent.  If it was only rendering the hyper key
useless, then maybe you could argue it as not being urgent, but it's
not merely that ... any attempt to assign the hyper function to any
other key (e.g. right alt), just adds the hyper function instead of
replacing the previous function with that.  So if left alt is meta and
you set right alt as hyper, it just becomes a combined hyper-meta.
It's no longer possible to set the hyper key on its own.

Which means the code commentary about changing the nil to none for all
those ns modifier keys is, in fact, completely wrong.  You *do* want nil
there because if you're re-assigning the key to perform another task
you actually do want to clear the original setting out of it.

As for a stable fix, that's dead simple, roll back everything from the
2016 commit that was merged into master on the 5th and it's done.

Anyway, I've got to wander off to one of those other pressing things
and since it involves a wee small hospital visit, it takes priority.
I'll try to take another look at this beast a little later.


Regards,
Ben

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2018-02-07  2:13 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 14:49 Emacs 26 MacOS bugs Richard Stallman
2018-02-06 17:30 ` Noam Postavsky
2018-02-06 23:28   ` Paul Eggert
2018-02-07  3:37     ` Eli Zaretskii
2018-02-10 14:55     ` Uwe Brauer
2018-02-10 15:18       ` Noam Postavsky
2018-02-07  3:52   ` Eli Zaretskii
2018-02-06 19:05 ` Ben McGinnes
2018-02-06 20:30   ` Noam Postavsky
2018-02-06 22:27     ` Ben McGinnes
2018-02-06 22:30       ` Ben McGinnes
2018-02-06 22:50       ` Noam Postavsky
2018-02-07  0:43         ` Ben McGinnes
2018-02-07  1:33           ` Noam Postavsky
2018-02-07  2:13             ` Ben McGinnes [this message]
2018-02-07 22:55               ` Alan Third
2018-02-09 16:35                 ` Ben McGinnes
2018-02-09 16:57                   ` Noam Postavsky
2018-02-09 17:22                     ` Ben McGinnes
2018-02-09 18:13                       ` Noam Postavsky
2018-02-10  1:46                         ` Ben McGinnes
2018-02-10  1:47                   ` Alan Third
2018-02-11 13:53                 ` Philipp Stephani
2018-02-11 21:06                   ` Alan Third
2018-02-07 20:01     ` Alan Third
2018-02-10 15:01     ` Alan Third
2018-02-10 22:45 ` Alan Third
2018-02-11 11:47   ` Alan Third
2018-02-11 15:52     ` Eli Zaretskii
2018-02-11 20:57       ` Alan Third
2018-02-13 19:41         ` Ben McGinnes
2018-02-13 19:46           ` Noam Postavsky
2018-02-11 20:43   ` Richard Stallman

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=20180207021301.zpvpexdkewztqxo4@adversary.org \
    --to=ben@adversary.org \
    --cc=emacs-devel@gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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.