From: Richard Stallman <rms@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: eliz@gnu.org, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
rpluim@gmail.com
Subject: Re: scratch/emoji vs emacs that maybe canʼt display emojis
Date: Tue, 09 Nov 2021 06:37:06 -0500 [thread overview]
Message-ID: <E1mkPR4-0004Ei-OY@fencepost.gnu.org> (raw)
In-Reply-To: <87wnljd0ab.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 08 Nov 2021 00:16:28 +0100)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I like the plan, but surely there must be a way to also involve a
> service from Google here somehow, so that we can get special
> personalised ad emojis, too.
It's not acceptable to make Emacs depend on a network service in order
to do its job. It must be able to work on a computer with no net
connention -- not only so that it works for you when you don't have a
net connection, but also so that users have full control over its
behavior.
In the specific case of Google, its dis-services are likely to have
unjust requirements in their terms and conditions. If so, it would
be wrong for us to suggest that users accept those conditions.
We will not do that.
The only acceptable way to do this is to write or find free code to do
the job, and include that in or with Emacs.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2021-11-09 11:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 8:22 scratch/emoji vs emacs that maybe canʼt display emojis Robert Pluim
2021-11-05 11:57 ` Eli Zaretskii
2021-11-05 13:38 ` Robert Pluim
2021-11-05 14:25 ` Eli Zaretskii
2021-11-05 14:35 ` Robert Pluim
2021-11-06 14:30 ` Benjamin Riefenstahl
2021-11-05 14:30 ` Lars Ingebrigtsen
2021-11-05 14:38 ` Robert Pluim
2021-11-05 14:39 ` Lars Ingebrigtsen
2021-11-07 16:05 ` Lars Ingebrigtsen
2021-11-07 16:12 ` Lars Ingebrigtsen
2021-11-07 16:30 ` Eli Zaretskii
2021-11-07 20:48 ` Lars Ingebrigtsen
2021-11-07 22:31 ` Stefan Monnier
2021-11-07 23:16 ` Lars Ingebrigtsen
2021-11-09 11:37 ` Richard Stallman [this message]
2021-11-09 23:40 ` Lars Ingebrigtsen
2021-11-11 3:39 ` scratch/emoji vs emacs that maybe canʼt " Richard Stallman
2021-11-11 3:44 ` scratch/emoji vs emacs that maybe canʼt " Lars Ingebrigtsen
2021-11-12 4:23 ` Richard Stallman
2021-11-14 5:17 ` David Masterson
2021-11-14 5:24 ` Lars Ingebrigtsen
2021-11-16 3:24 ` David Masterson
2021-11-11 13:26 ` Po Lu
2021-11-11 15:15 ` Eli Zaretskii
2021-11-11 19:22 ` Stefan Monnier
2021-11-11 19:32 ` Eli Zaretskii
2021-11-12 0:42 ` Po Lu
2021-11-08 0:39 ` scratch/emoji vs emacs that maybe canʼt " Tim Cross
2021-11-07 16:34 ` Benjamin Riefenstahl
2021-11-07 18:29 ` Eli Zaretskii
2021-11-07 16:25 ` Eli Zaretskii
2021-11-08 10:31 ` Robert Pluim
2021-11-08 10:33 ` Lars Ingebrigtsen
2021-11-08 10:52 ` Robert Pluim
2021-11-09 3:31 ` Lars Ingebrigtsen
2021-11-09 10:14 ` Robert Pluim
2021-11-08 13:16 ` Eli Zaretskii
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=E1mkPR4-0004Ei-OY@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@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).