From: Po Lu <luangruo@yahoo.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: ns-do-applescript
Date: Wed, 25 May 2022 12:46:31 +0800 [thread overview]
Message-ID: <87tu9ejk2g.fsf@yahoo.com> (raw)
In-Reply-To: <87k0aamhgw.fsf@gmail.com> (Tim Cross's message of "Wed, 25 May 2022 12:58:41 +1000")
Tim Cross <theophilusx@gmail.com> writes:
> This might be a reaonable argument when considering adding additional
> support/integration, but falls short when referencing work which ahs
> already been completed and has been part of Emacs for some time.
If such a feature lands by mistake, our policy is to remove it until it
is also available on a free system. That has happened many times, most
recently with "tabbed windows" and color fonts on macOS.
> Perhaps then your not the right person to address those bugs? Perhaps
> they need to be addressed by someone who does actually use that
> platform?
Unfortunately, the "someone who does actually use that platform"
recently quit.
> The argument that leaving such functionality in place will encourage
> users to use it seems somethwat flawed. This functionality is only
> available if your running on that platform and if your already running
> on that platform, encouragement to run on that platform doesn't amount
> to much. I would also suggest far more enrouagement comes from having
> support to build Emacs on that platform in the first place.
>
> It is also possible that having this support means users can actually
> use Emacs to perform some tasks which would otherwise require closed
> proprietary solutions or which would be easier to do with close
> properietary solutions. Maybe this support actually enrouages users to
> use Emacs instead of a non-free editor which has applescript support?
That horse is already dead, and this is neither the place nor the time
to beat it.
next prev parent reply other threads:[~2022-05-25 4:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Po Lu [this message]
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-31 6:34 ns-do-applescript Pedro Andres Aranda Gutierrez
2022-05-31 23:08 ` ns-do-applescript Stefan Monnier
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
[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 ` ns-do-applescript Po Lu
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
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=87tu9ejk2g.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=theophilusx@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).