From: Christopher Dimech <dimech@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs Manual under a categorisation scheme
Date: Tue, 12 Jul 2022 19:16:35 +0200 [thread overview]
Message-ID: <trinity-ef19a1a7-dd1e-4562-a148-d0ee8dcc148c-1657646195296@3c-app-mailcom-bs07> (raw)
In-Reply-To: <83pmiaw9aa.fsf@gnu.org>
> Sent: Wednesday, July 13, 2022 at 5:06 AM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: emacs-devel@gnu.org
> Subject: Re: Emacs Manual under a categorisation scheme
>
> > From: Christopher Dimech <dimech@gmx.com>
> > Cc: emacs-devel@gnu.org
> > Date: Tue, 12 Jul 2022 18:57:20 +0200
> >
> > > I don't think I understand what kind of category system do you have in
> > > mind. Please elaborate and/or show an example.
> >
> > One could arrange either by difficulty or frequency.
> >
> > Basically, using a higher level categorisation to the 54 chapters, with each
> > high level category being independent of the others. One can then quickly
> > skip whole categories one is not interested in, even when using the manual on
> > the website.
> >
> > 1. Comprehending the Graphical Display
> > 2. Running Commands (by Name, using Minibuffer read and completion)
> > 3. Editing Commands (moving and killing text)
> > 4. Using and Controlling the Graphical Display (buffer, window, frame)
> > 5. Major and Minor Modes
> > 6. Using Help
> > 7. Programming and Markup Modes
> > 8. Compiling, Testing, and Maintaining Programs
> > 9. Running Shell Commands
> > 10. Calendar, Diary, Document Viewing
> > 10. Web Applications (EWW, Mail)
> > 11. Emacs Customisation
> > 12. Handling Problems (crashes, reporting bugs)
>
> I don't see how this is significantly different from the chapters we
> have now. You can categorize Emacs in any number of ways, but the one
> we have is IMNSHO completely adequate. What you propose is also
> adequate (although incomplete, so I cannot easily judge it except as
> an example), but I don't see why it is superior.
>
Yes, it is as an example as I agree it is not complete. It is a higher
level categorisation without changing the actual chapters you have now.
It was a response on some user comments stating that the whole lot looks
overwhelming.
You could also make a number of scenarios on what the user wants to search
so he can be directed to the relevant information faster.
next prev parent reply other threads:[~2022-07-12 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 16:13 Emacs Manual under a categorisation scheme Christopher Dimech
2022-07-12 16:27 ` Eli Zaretskii
2022-07-12 16:45 ` [External] : " Drew Adams
2022-07-12 16:57 ` Christopher Dimech
2022-07-12 17:06 ` Eli Zaretskii
2022-07-12 17:16 ` Christopher Dimech [this message]
2022-07-12 17:23 ` Eli Zaretskii
2022-07-12 17:52 ` Christopher Dimech
2022-07-13 3:18 ` Richard Stallman
2022-07-13 3:56 ` Christopher Dimech
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-ef19a1a7-dd1e-4562-a148-d0ee8dcc148c-1657646195296@3c-app-mailcom-bs07 \
--to=dimech@gmx.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.