From: David Reitter <david.reitter@gmail.com>
To: Anders Lindgren <andlind@gmail.com>
Cc: Keith David Bershatsky <esq@lawlist.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: bug #18283 / change "Enable applescript in NextStep"
Date: Wed, 25 Nov 2015 07:02:45 -0500 [thread overview]
Message-ID: <69D2E076-BF98-442F-9CC8-EE9F94AA1262@gmail.com> (raw)
In-Reply-To: <CABr8ebbYFa31gEgZbKz4w7HwCtN32Jirdy4f5gcARvLEuqrLrQ@mail.gmail.com>
Anders,
Thank you. That sounds like a good change then, but I needed your explanation to understand.
- David
> On Nov 25, 2015, at 12:44 AM, Anders Lindgren <andlind@gmail.com> wrote:
>
> Hi,
>
> This change allows applescripts like the following to work:
>
> tell application "Emacs"
> set the bounds of the first window to {100, 100, 500, 500}
> end tell
>
> Without the change, the following error message is issued:
>
> test.oas:23:89: execution error: Emacs got an error: Can’t set bounds of window 1 to {100, 100, 500, 500}. (-10006)
>
> However, after the change, Emacs repositions and resizes its frame nicely.
>
>
> So, the reporter of bug #18283 literally requested this change, but I think that may have just been a somewhat silly way to say: “Can you please support AppleScript?”
>
> But perhaps I’m misunderstanding all of this and there’s a grand master plan.
>
> The original poster asked for this change in order to write automatic tests for the NextStep user interface. Concretely, it was used to verify that the recent problems with tool-bar-mode setting the wrong frame size was solved. I am absolutely sure that he did not implicitly expected a full AppleScript interface to be implemented.
>
> -- Anders Lindgren
>
prev parent reply other threads:[~2015-11-25 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 2:50 bug #18283 / change "Enable applescript in NextStep" David Reitter
2015-11-25 5:44 ` Anders Lindgren
2015-11-25 12:02 ` David Reitter [this message]
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=69D2E076-BF98-442F-9CC8-EE9F94AA1262@gmail.com \
--to=david.reitter@gmail.com \
--cc=andlind@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=esq@lawlist.com \
/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.