unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: chad <yandros@gmail.com>
Cc: Richard Stallman <rms@gnu.org>,
	 EMACS development team <emacs-devel@gnu.org>
Subject: Re: ns-do-applescript
Date: Wed, 01 Jun 2022 08:35:20 +0800	[thread overview]
Message-ID: <87mtex8blj.fsf@yahoo.com> (raw)
In-Reply-To: <CAO2hHWYf9BUiEWodg4YfgkFX0vendxZK6L0-=BFT+ZBtePiCPQ@mail.gmail.com> (chad's message of "Tue, 31 May 2022 15:05:48 -0400")

chad <yandros@gmail.com> writes:

> From my point of view, this pretty clearly falls into the category of
> native application support on a proprietary OS. It's not enabling
> anything that doesn't already exist, by definition; but it is
> potentially making life easier for Emacs users on that platform. In
> practice, there wasn't a lot of upside when last I looked, so it
> probably doesn't warrant a lot of effort to continue, but there are a
> few platform-standard things that it enables that are useful and
> benefit from calling a library function rather than forking an
> interpreter. Of course, that relies on there being someone willing to
> maintain the glue to those library functions.

From my POV, it is easily replaced by running `osascript' in a
subprocess, and the features provided by the so-called "native
application support" are not available on free operating systems.  It
also comes with various disadvantages, such as quitting being disabled
while the script is running, which isn't the case inside subprocesses.



  reply	other threads:[~2022-06-01  0:35 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87bkvoo38y.fsf.ref@yahoo.com>
2022-05-23 12:14 ` ns-do-applescript Po Lu
2022-05-23 20:44   ` ns-do-applescript Filipp Gunbin
2022-05-24  0:26     ` ns-do-applescript Po Lu
2022-05-24 20:00       ` ns-do-applescript Daniel Martín
2022-05-24 20:11         ` ns-do-applescript Stefan Monnier
2022-05-25 13:57           ` ns-do-applescript Howard Melman
2022-05-26  8:27             ` ns-do-applescript Richard Stallman
2022-05-26 14:03               ` ns-do-applescript Howard Melman
2022-05-26 14:17                 ` ns-do-applescript Andreas Schwab
2022-05-26 14:51                   ` ns-do-applescript Howard Melman
2022-05-26 15:36                     ` ns-do-applescript Andreas Schwab
2022-05-26  8:24       ` ns-do-applescript Richard Stallman
2022-05-26  8:49         ` ns-do-applescript Po Lu
2022-05-27 22:49           ` ns-do-applescript Richard Stallman
2022-05-28  0:43             ` ns-do-applescript Po Lu
2022-05-29 21:21               ` ns-do-applescript Richard Stallman
2022-05-29 23:56                 ` ns-do-applescript Po Lu
2022-05-31 19:05                   ` ns-do-applescript chad
2022-06-01  0:35                     ` Po Lu [this message]
2022-06-01  1:10                       ` ns-do-applescript Stefan Monnier
2022-06-01 22:57                     ` ns-do-applescript Richard Stallman
2022-05-24 21:26     ` ns-do-applescript Richard Stallman
2022-05-24 23:01       ` ns-do-applescript Filipp Gunbin
2022-05-25  0:50       ` ns-do-applescript Po Lu
2022-05-25 12:09         ` ns-do-applescript Alexander Adolf
2022-05-24 21:21 ns-do-applescript Jon Snader
2022-05-25  2:28 ` ns-do-applescript Po Lu
2022-05-25  2:58   ` ns-do-applescript Tim Cross
2022-05-25  4:46     ` ns-do-applescript Po Lu
2022-05-25 10:05       ` ns-do-applescript Filipp Gunbin
2022-05-25 11:42       ` ns-do-applescript Pankaj Jangid
  -- strict thread matches above, loose matches on Subject: below --
2022-05-26 11:01 ns-do-applescript Pedro Andres Aranda Gutierrez
2022-05-26 14:07 ` ns-do-applescript Howard Melman
2022-05-26 15:07 ` ns-do-applescript Stefan Monnier
2022-05-27  9:40   ` ns-do-applescript Pedro Andres Aranda Gutierrez
2022-05-31  6:34 ns-do-applescript Pedro Andres Aranda Gutierrez
2022-05-31 23:08 ` ns-do-applescript Stefan Monnier

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=87mtex8blj.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=yandros@gmail.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 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).