From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 68963@debbugs.gnu.org
Subject: bug#68963: 30.0.50; [PATCH] Split Eshell built-in command documentation into subsections
Date: Wed, 07 Feb 2024 14:54:41 +0200 [thread overview]
Message-ID: <86eddozb72.fsf@gnu.org> (raw)
In-Reply-To: <7ba997dc-80ed-1915-0953-e013fa8a7162@gmail.com> (message from Jim Porter on Tue, 6 Feb 2024 20:26:08 -0800)
> Date: Tue, 6 Feb 2024 20:26:08 -0800
> Cc: 68963@debbugs.gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
>
> On 2/6/2024 7:31 PM, Eli Zaretskii wrote:
> >> Date: Tue, 6 Feb 2024 16:02:32 -0800
> >> From: Jim Porter <jporterbugs@gmail.com>
> >>
> >> Currently, the Eshell manual lists all the built-in commands in one
> >> section, which can make it hard to find the commands related to the
> >> topic you care about. Here's a patch to split this into subsections of
> >> various (loosely-defined) topics.
> >
> > If people look for commands by using 'i' (Info-index), then finding
> > them in a single long section will be as easy as doing that in several
> > shorter ones.
>
> The use-case I was imagining for this was a person thinking, "What
> commands does Eshell have for working with [say] directories?"
But then subdivision into sections has other problems. For example,
who says that 'ls' is only "for directories", ln, mv, and rm are only
"for files", and info is "for searching"? A person can reasonably
think about these (and others) differently. And why "basename" is not
about files?
That is why we use indexing for providing flexible and accurate search
capabilities: you can have more than one index entry for each piece of
text, so you can satisfy different use cases where people have
different phrases on their mind when thinking about something.
So the right way of handling this is to use better indexing. You
could index each command, for example:
@cindex deleting files and directories
@cindex file commands, deletion
[text about 'rm' here]
and in addition, you could have a short section with a list of
"file-related commands", where each command or group of commands is
followed by a cross-reference to the relevant place/section.
Using sectioning for these purposes is not flexible enough to satisfy
enough use cases, because it supports only a single way of looking at
a subject, and people tend to think about them differently, especially
if they need that in different contexts.
next prev parent reply other threads:[~2024-02-07 12:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 0:02 bug#68963: 30.0.50; [PATCH] Split Eshell built-in command documentation into subsections Jim Porter
2024-02-07 3:31 ` Eli Zaretskii
2024-02-07 4:26 ` Jim Porter
2024-02-07 12:54 ` Eli Zaretskii [this message]
2024-02-07 20:22 ` Stefan Kangas
2024-02-08 2:05 ` Jim Porter
2024-02-08 7:07 ` Eli Zaretskii
2024-02-08 20:30 ` Jim Porter
2024-02-09 7:05 ` Eli Zaretskii
2024-02-10 1:44 ` Jim Porter
2024-02-08 21:32 ` Stefan Kangas
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=86eddozb72.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68963@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
/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).