unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: psainty@orcon.net.nz, 56510@debbugs.gnu.org
Subject: bug#56510: Make some games obsolete (or just remove them from the menu)
Date: Tue, 12 Jul 2022 16:28:08 +0300	[thread overview]
Message-ID: <83lesyxxxz.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmknD8Cv2DHZ9aVcpYQXGgWc1=MgFY7n=TgLHK92++2hCg@mail.gmail.com> (message from Stefan Kangas on Tue, 12 Jul 2022 04:54:45 -0500)

> Cc: 56510@debbugs.gnu.org
> From: Stefan Kangas <stefan@marxist.se>
> Date: Tue, 12 Jul 2022 04:54:45 -0500
> 
> Phil Sainty <psainty@orcon.net.nz> writes:
> 
> > On 2022-07-12 15:06, Stefan Kangas wrote:
> >> Some of the games in Emacs look a bit dated.  I put it to you that they
> >> are not excellent promotion for Emacs, and that we are better served by
> >> having fewer but better games.
> >
> > Why do they need to be "an excellent promotion for Emacs" as opposed
> > to "games you can play"?
> 
> I was trying to be polite, sorry.  Let me put it a bit more bluntly:
> they make Emacs look scruffy and antiquated, and should much sooner be
> hidden than actively promoted.

Aren't you exaggerating a bit?  How can a game make Emacs look
"scruffy and antiquated"?  And how can removing some games without
adding anything in their stead make Emacs look better?

If you (or someone else) personally don't like those games, you are
welcome not to play them.  But why force your views on others in such
a blatant way?





  reply	other threads:[~2022-07-12 13:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12  3:06 bug#56510: Make some games obsolete (or just remove them from the menu) Stefan Kangas
2022-07-12  3:45 ` Visuwesh
2022-07-12  8:27 ` Phil Sainty
2022-07-12  9:54   ` Stefan Kangas
2022-07-12 13:28     ` Eli Zaretskii [this message]
2022-07-12 13:29     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-12 15:13     ` Drew Adams
2022-07-12 15:56       ` Stefan Kangas
2022-07-12 16:23         ` Drew Adams
2022-07-13  3:18           ` Richard Stallman
2022-07-13 16:47             ` Drew Adams
2022-07-13 22:58             ` Jean Louis
2022-07-15  3:34               ` Richard Stallman
2022-07-12 13:09 ` Lars Ingebrigtsen
2022-07-12 14:04   ` Stefan Kangas
2022-07-12 14:23     ` Eli Zaretskii
2022-07-12 14:36       ` Eli Zaretskii
2022-07-12 14:38       ` Stefan Kangas
2022-07-12 13:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=83lesyxxxz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=56510@debbugs.gnu.org \
    --cc=psainty@orcon.net.nz \
    --cc=stefan@marxist.se \
    /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).