[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Should this package be included into the NS port?

From: Alan Third
Subject: Re: Should this package be included into the NS port?
Date: Sat, 2 Jun 2018 21:11:35 +0100
User-agent: Mutt/1.9.3 (2018-01-21)

On Sat, Jun 02, 2018 at 03:39:19PM -0400, Stefan Monnier wrote:
> > <268435468> is undefined
> Hmm... that is a weird event, indeed.
> [ No surprise you can't "catch the error", because it's not an `error`:
>   you just end up running the `undefined` command which emits this
>   message and beeps.  ]

I’m pretty sure that number is the one defined in nsterm.h line 751:

    #define KEY_NS_NEW_FRAME               ((1<<28)|(0<<16)|12)

and it looks like it’s defined for lisp in x-setup-function-keys in
common-win.el, but it looks to me like it should be set up in all
frames where (featurep 'ns) is true.

If I run emacsclient -nw (featurep 'ns) returns true, but the event
appears to be undefined (just shows the number).

Oh, I just read the docstring:

    "Set up `function-key-map' on the graphical frame FRAME."

I guess that function doesn’t run on terminal frames, then. That might
explain it.

Would we be able to define this (or maybe all of the NS events?) in
ns-win.el instead of in this function? Would that be a bad idea?
Alan Third

reply via email to

[Prev in Thread] Current Thread [Next in Thread]