From: Adrian Robert <adrian.b.robert@gmail.com>
To: mituharu@math.s.chiba-u.ac.jp
Cc: Ken Raeburn <raeburn@gnu.org>, emacs-devel@gnu.org
Subject: Re: a little feedback on Cocoa Emacs.app
Date: Mon, 4 Aug 2008 09:08:59 -0400 [thread overview]
Message-ID: <B242BD84-2622-44E6-BCA7-847053BBFC75@gmail.com> (raw)
In-Reply-To: <50642.203.180.89.51.1217853759.squirrel@weber.math.s.chiba-u.ac.jp>
On Aug 4, 2008, at 8:42 AM, mituharu@math.s.chiba-u.ac.jp wrote:
>> +- (void)newFrame: (id)sender
>> +{
>> + Feval (Fcons (intern ("make-frame"), Qnil));
>> +}
>> +
>
> Strictly speaking, Feval calls inside read_socket_hook are not
> allowed by design, although the Cocoa/GNUstep port is using it
> extensively...
Yes.. I was going to change this to use an alternative method similar
to your patch below before committing. And the other Fevals are still
slated for removal -- just been a lot of higher-priority items since
the previous discussion.
> err = AppendMenuItemTextWithCFString (menu, CFSTR ("New Frame"),
> 0, kHICommandNew, NULL);
> ...
> (put 'new 'mac-apple-event-id "new ") ; kHICommandNew
> (define-key mac-apple-event-map [hi-command new] 'make-frame)
next prev parent reply other threads:[~2008-08-04 13:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 2:11 a little feedback on Cocoa Emacs.app Ken Raeburn
2008-07-27 2:29 ` Adrian Robert
2008-07-27 2:56 ` Stefan Monnier
2008-07-27 16:45 ` Ken Raeburn
2008-07-28 2:34 ` Adrian Robert
2008-08-04 10:15 ` Ken Raeburn
2008-08-04 12:42 ` mituharu
2008-08-04 13:08 ` Adrian Robert [this message]
2008-08-04 12:50 ` Adrian Robert
2008-08-04 16:56 ` Ken Raeburn
2008-08-04 17:04 ` Dan Nicolaescu
2008-08-04 17:23 ` Justin Bogner
2008-08-04 17:27 ` Dan Nicolaescu
2008-08-04 19:28 ` Ken Raeburn
2008-08-04 21:53 ` Dan Nicolaescu
2008-08-04 23:43 ` Adrian Robert
2008-08-05 3:05 ` Adrian Robert
2008-08-05 4:01 ` Ken Raeburn
2008-08-05 16:17 ` Adrian Robert
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B242BD84-2622-44E6-BCA7-847053BBFC75@gmail.com \
--to=adrian.b.robert@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
--cc=raeburn@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).