[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: George Plymale II
Subject: Re: Should this package be included into the NS port?
Date: Tue, 22 May 2018 16:09:28 -0400

Alan Third <address@hidden> writes:

> Sorry, yes. I’ve only got limited time for Emacs at the moment, so I’m
> being a bit slow in responding.

No problem, I was just unsure if you saw Stefan's message.

> This does help, though.
> It seems that if you end up in the situation where you’ve only got the
> terminal left you can use
>     (make-frame-on-display (car (x-display-list)))
> to create a new GUI frame, but the problem now is that the Emacs event
> the dock menu fires (ns-new-frame) is only available in NS frames (or
> something, I’m unclear), so if the current frame is a terminal frame,
> and you click on ‘new frame’ in the dock menu, the terminal displays
>     <268435468> is undefined
> I assume what we need to do is define the ns-new-frame event somewhere
> other than nsterm.h, which is where it is now.
> This all sounds wrong to me, tbh. But I don’t know of any other way we
> can run lisp from within the NSApp run loop than by firing off events
> or setting a flag and catching it later.

Hmm, very interesting. Yes, all of what you're saying makes sense
although it does perhaps seem a bit "wrong" as you say. Nonetheless, a
"wrong" solution may be better than no solution. Just my 2¢

- George Plymale II

reply via email to

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