unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Summer Emacs <summeremacs@summerstar.me>
Cc: emacs-devel@gnu.org
Subject: Re: "About Emacs" page
Date: Sun, 22 Sep 2024 00:09:45 -0400	[thread overview]
Message-ID: <E1ssDur-00023n-0B@fencepost.gnu.org> (raw)
In-Reply-To: <EC6E881B-83B0-40F2-9594-BC263604E483@summerstar.me> (message from Summer Emacs on Thu, 19 Sep 2024 12:19:53 +0200)

[[[ 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. ]]]

  > Sure! I’m talking about the About Emacs page you first see when
  > you boot up Emacs the first time. (C-h C-a). I will detail more
  > thoughts about it in another email in the thread.

That page is the way it is because there is a lot of information we
want to show people right at the start.  Some for our purposes, some
because users (not ONLY NEW users!) may find it helpful.  We tried to
set up this page to make those things prominent and easy to find.

  > 2) GNU and Freedom - There’s a philosophy here about Emacs, I
  > recognise that, but is it really what most people want to read about
  > when they first open up Emacs?

Teaching people this philosophy is high priority for us.  Emacs is
part of the GNU system. and giving freedom is he purpose of the GNU
system.  So it behooves us to present that in a prominent way.

This is not necessarily the only way or place to present it.
If we see a better way or place, we can switch to that.  Or do both.

  > Getting into the philosophy of Emacs might be important (I
  > think it is at times), but it’s not foremost on people’s minds when
  > they first open Emacs.

The hope is that reading about that issue will make it foremost on
people’s minds, or at least closer to foremost.

  > 3) Absence of Warranty - Okay. Legal. Important to understand but..a
  > little scary. If you’re trying a new product, you don’t want one of
  > the FIRST things you see to say “use at your own risk”.

Our legal advice was to make this very visible.  We must do so.

  > 5) Getting New Versions - Good link to have, not so helpful at the top
  > though. Put it at the bottom below the Emacs philosophy/legal section.

  > 6) Ordering Manuals - This is good! But, it should be under the new
  > users/Emacs tutorials in the same grouping. It makes sense to put it
  > there as it’s the same subject. It’ll still be in the top section that
  > way but grouped better.

  > 7) Emacs Tutorial - That should be right at the top below the new
  > newbie section which I plan on finishing sometime in the coming
  > weeks. The newbie section will also have a link to the Emacs tutorial
  > and info about how to get back to the newbie pages.

  > 9) Emacs Manual - Good. I like. In depth, interesting, but very
  > difficult for a new user to read through. They have to understand the
  > basics first. I think that should go right under the Emacs tutorial
  > which would be right under the newbie users section at the top.

These changes could be considered.  Where to put them is significant
only in a practical way; if a different placement works better, that's
fine to change.

  > 8) Emacs Guided Tour - this is, again, is a great section,
  > however…it’s confusing to new users (as explained in one of my last
  > emails). It should be near the bottom of the top section because it’s
  > not *really* a guided tour.

Should we change its contents to make it a real guided tour?
Should we call it something else that fits the facts better?
What name do you suggest?

-- 
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)





  parent reply	other threads:[~2024-09-22  4:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 10:19 "About Emacs" page Summer Emacs
2024-09-19 12:57 ` Philip Kaludercic
2024-09-20  2:47   ` Emanuel Berg
2024-09-20  6:41     ` Eli Zaretskii
2024-09-20  7:09       ` Juergen Fenn
2024-09-20  7:41         ` Juergen Fenn
2024-09-20  7:52           ` Summer Emacs
2024-09-20  8:55             ` Emanuel Berg
2024-09-20 10:23           ` Eli Zaretskii
2024-09-20 12:23             ` Juergen Fenn
2024-09-20  8:34         ` Ulrich Mueller
2024-09-20 10:27           ` Eli Zaretskii
2024-09-20 15:52             ` Manuel Giraud via Emacs development discussions.
2024-09-20 17:34               ` Eli Zaretskii
2024-09-28  9:39               ` Eli Zaretskii
2024-09-28 10:55                 ` Ulrich Mueller
2024-09-28 11:40                   ` Eli Zaretskii
2024-09-22  4:09   ` Richard Stallman
2024-09-22 15:54     ` Philip Kaludercic
2024-09-24  3:31       ` Richard Stallman
2024-09-24 12:05         ` Philip Kaludercic
2024-09-20  7:00 ` Sławomir Grochowski
2024-09-20  7:57   ` Summer Emacs
2024-09-22  4:09 ` Richard Stallman [this message]
2024-09-22  5:26   ` Eli Zaretskii
2024-09-23 10:41     ` Summer Emacs

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=E1ssDur-00023n-0B@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=summeremacs@summerstar.me \
    /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).