unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: summeremacs@summerstar.me, emacs-devel@gnu.org
Subject: Re: "About Emacs" page
Date: Sun, 22 Sep 2024 08:26:44 +0300	[thread overview]
Message-ID: <86bk0g2r8r.fsf@gnu.org> (raw)
In-Reply-To: <E1ssDur-00023n-0B@fencepost.gnu.org> (message from Richard Stallman on Sun, 22 Sep 2024 00:09:45 -0400)

> From: Richard Stallman <rms@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Sun, 22 Sep 2024 00:09:45 -0400
> 
>   > 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.

They are all a dozen lines in a relatively small window.  One cannot
miss any of them when looking at that window.  We can argue about the
order till kingdom come, but eventually it makes very little
difference.  It isn't like the order says something about their
importance -- they are all important.

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

Before this happens, someone should write such a tour.  It's a
non-trivial job, to say the least, and my hat's off to whoever will be
bale to pull that.  For now, we have what we have, which isn't ideal,
but better than nothing.  And I don't see anything wrong with its
placement.



  reply	other threads:[~2024-09-22  5:26 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
2024-09-22  5:26   ` Eli Zaretskii [this message]
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=86bk0g2r8r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).