From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>, Po Lu <luangruo@yahoo.com>
Subject: RE: Re: ns-do-applescript
Date: Tue, 31 May 2022 08:34:01 +0200 [thread overview]
Message-ID: <CAO48Bk9VuZaFxnDtpeBMZdru4jHm5CcnNp3meWNSOhHk9H7ZnA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]
Message: 15
Date: Mon, 30 May 2022 10:50:10 +0800
From: Po Lu <luangruo@yahoo.com>
> To: Jon Snader <jcs@irreal.org>
> Cc: emacs-devel@gnu.org
> Subject: Re: Fwd: Re: ns-do-applescript
> Message-ID: <871qwbd999.fsf@yahoo.com>
> Content-Type: text/plain
> Jon Snader <jcs@irreal.org> writes:
...
>>> The ns-do-applescript call is (or could be considered) simply a call
>>> to an OS specific interface routine. It's useful for many things
>>> besides getting contacts and its presence in *in the macOS Emacs
>>> build* hurts no one, whereas its removal is sure to cause lots of
>>> inconvenience for Mac users and those writing packages for the
>>> platform.
> We don't want to make things convenient for Mac users, when those things
> are not possible on a free system. Just as Emacs doesn't provide
> "OS-specific interface routines" to perform tasks on non-free operating
> systems that are not possible on free ones.
<flagelante>
Yes, I repent, I confess... I use Emacs on a macOS...
</flagelante>
as I write shell scripts (bash/zsh), gawk, Inkscape, GIMP, LaTEX, etc.
Exactly the same way I do this on my Linux system(s) and on the VMs I
create and share.
And while I'm using DBus in Linux for forward/backward searching between
*TeX and PDF, I do use ns-do-applescript for some of that magic on macOS.
Same goes for bringing the Emacs window to the top of the desktop and for
other functions.
I think all the traffic started because someone asked whether a pure elisp
alternative to ns-do-applescript could be found and call-process to
osascript was proposed. Humbly yours showed how to do such a thing (at
least on my very rudimentary use of osascript).
So, yes, you can write it in ELisp, but I can't tell you whether it makes
sense to scare people away from Emacs by not providing functionality
(IMvvHO that would be a pity). The argument "now you see what you could be
doing in Linux" has already given some fruits in my experience.
Best, /PA
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
[-- Attachment #2: Type: text/html, Size: 3112 bytes --]
next reply other threads:[~2022-05-31 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 6:34 Pedro Andres Aranda Gutierrez [this message]
2022-05-31 23:08 ` ns-do-applescript Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2022-05-26 11:01 ns-do-applescript Pedro Andres Aranda Gutierrez
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=CAO48Bk9VuZaFxnDtpeBMZdru4jHm5CcnNp3meWNSOhHk9H7ZnA@mail.gmail.com \
--to=paaguti@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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).