all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 18:57:20 +0200	[thread overview]
Message-ID: <trinity-46c2356b-8c8f-472d-b66c-3d4fbc2df401-1657645040011@3c-app-mailcom-bs07> (raw)
In-Reply-To: <83sfn6wb38.fsf@gnu.org>


> Sent: Wednesday, July 13, 2022 at 4:27 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>
> > Date: Tue, 12 Jul 2022 18:13:55 +0200
> > Sensitivity: Normal
> >
> > With the Emacs Manual having 54 sections, could it be be categorised under a much smaller
> > scheme (perhaps five or eight).  This is to easily and quickly go through it for the
> > information one wants by using a category system.
>
> 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)



> > For instance, the GNU Manuals Online is arranged by a limited number of categories.
> > See https://www.gnu.org/manual/manual.html
>
> This has about 40 categories: not a far cry from our 54 chapters.
>
> To look for some subject, one is supposed to use the Info-index
> command, bound to 'i' inside Info.  There's no need to look up
> subjects by reading the chapter titles.
>



  parent reply	other threads:[~2022-07-12 16:57 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 [this message]
2022-07-12 17:06     ` Eli Zaretskii
2022-07-12 17:16       ` Christopher Dimech
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-46c2356b-8c8f-472d-b66c-3d4fbc2df401-1657645040011@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.